SRU: updates necessary for Kubuntu Upgrade Tool in Edgy

packages for testing at

http://kubuntu.org/~jriddell/tmp/edgy-dist-upgrade/

This adds the features to pykde and adept necessary to run the dist-upgrade tool.

kdelibs and kdebase get new functions to attach another process's pty to konsole (kpty). pykde gets support for the konsole kpart. Finally Adept adds a wizard to download the dist-upgrade tool and run it. Adept is also patched to stop it forking (KUniqueApplication), this allows it to start new X processes since otherwise it looses xauthority permissions.

Impact: users get a way to upgrade Kubuntu sanely, otherwise they have to try their luck with dist-upgrade, which usually doesn't work.

attached effective code diff for easier review

Review of kdebase packaging bits:
- please include the bug number and a detailled description of the code changes into the changelog
- this adds a new function, thus this needs a shlibs bump

I do not have intimate knowledge of the code, but the code changes look sane, have been tested in Feisty, and only add new functions, thus existing software will not be affected when it breaks. Thus code patch is ok.

attached effective code diff for easier review

Review of kdelibs packaging bits:
  - please include the bug number and a detailled description of the code changes into the changelog
  - this adds a new function, thus this needs a shlibs bump

The patch is very messy -- is it possible to rearrange the changes to minimize it? right now it seems to move the open() function to a different place whcih generates a lot of noise and thus it's very hard to check.

python-kde review:

- Detailled explanation of the changes in the changelog, please.
- no updated build/binary dependencies for the new kdelibs API?
- Why is the configure.py change necessary and why was the code commented out before?
- The konsole_part.sip looks strange to me: it seems that this just converts the 3.4.1 version to the 3.5.2 version, but that (a) certainly does not reflect the changes in kdelibs/kdebase (which just got the new 'pass pty through fd' feature added) and (b) seems much more intrusive than necessary. Shouldn't it be enough to add the new setPty() function to the interface? In any case this is certainly not a minimal diff.

adept review:

- Detailled explanation of the changes in the changelog, please.
- No updated build/binary dependencies for the new kdelibs API?
- kubuntu_08_no_unique_application.diff: funny that an 'unique' app forks where a non-unique doesn't :) can you elaborate about this change a bit? (preferably in the changelog); anyway, this looks innocent enough, I trust your testing and KDE code experience for this patch.
- kubuntu_02_dist_upgrader.diff: entirely new code, I cannot verify correctness; however, integration into existing code parts looks sane, thus this should be heavily tested before allowing this in to edgy stable.

This entire update makes me nervous as hell, though. I would not normally consider it SRU-worthy. I will consider myself overruled if:
 - above points get solved
 - the patches are reviewed by a second person with KDE programming skills
 - I get explicit confirmation from mdz and the Kubuntu community that we really, really want this feature for edgy already, at the risk of breaking existing applications.
 - We get written feedback (as bug comments) from at least 10 different testers (using different languages, mirrors, a local mirror, etc.) that these changes do not break the existing functionality of adept, correctly upgrade edgy to Feisty (modulo Feisty package bugs, of course), and other KDE applications (C++ and Python ones).

Updated kdelibs patch with better explanation in changelog and updated shlibs

Updated kdebase patch with better explanation in changelog, updated shlibs version.

Add better description in changelog and missing build-deps.

Add better description in changelog and change patch to fix working directory on process.

Updated patches attached above.

The diff in kdelibs is as minimal as possible, the open() function has not been moved, it's just the added functions have some of the same lines of code so diff gets confused.

The diff in python-kde3 is also minimal, the edgy python-kde3 has some old unused files from a previous attempt to include konsole part in KDE 3.4 time, these files need to be updated for KDE 3.5, along with the code that has to be re-enabled in configure.py so the build system can find the konsolepart.so library.

Moving the added methods below the open() method in the kdelibs patch makes the diff much nicer. New kdelibs debdiff attached.

kdebase patch looks good now, thanks!

kdelibs:
- packaging looks good now
- in this kpty.cpp patch snippet

  gotpty:
+ return _attachPty(d->masterFd);
+
+ return true;
+}

  the second return is unnecessary and looks confusing, but it's just cosmetical.

- will the code alter the default behaviour in the function where this code snippet is from? _attachPty() does some additional things that the original function didn't do, in particular either grantpt(d->masterFd); or ::close(d->masterFd); this looks like if it would alter the current behaviour of unrelated programs. Can you elaborate about this, please (preferably in the changelog)?

- are the kdwarnings displayed by default? this looks like left-over debugging stuff

python-kde3: intrusive, but accepted since it is more or less just newly introduced glue for konsole that does not touch existing interfaces.

adept:
- kubuntu_08_no_unique_application.diff: since this does not enforce a single instance any more, what happens if adept is started multiple times?
- rest looks okay (modulo introducing lots of new code, but that's the point of this whole exercise after all)

TODO list:
 - Please answer the questions in comment 18, comment 19, and this one
- get a general 'yes, we want this in edgy and will put some serious time into it for testing' approval from the Kubuntu community and from Matt.
- (extensive testing should be done with -proposed, not right now yet)

kdelibs patch which duplicates code from open() in attachPty() rather than move it, makes it clear that the open() function has not been modified.

kdelibs patch again, with debugging statements removed.

Re: comment 20. If Adept is started more than once it warns the user and opens in read only mode, same as it always has done if you start it while apt-get or another dpkg programme is being used.

This patch doesn't kill Adept when running dist-upgrade tool. That was also blocking the xauthority permissions from allowing the new app to connect to X.

Alright, patches look reasonable now, thanks for cleaning them up. The following patches are approved for edgy-proposed:

http://librarian.launchpad.net/6536952/kdelibs_3.5.5-0ubuntu3.2.debdiff
http://librarian.launchpad.net/6475922/kdebase_3.5.5-0ubuntu3.3.debdiff
http://librarian.launchpad.net/6475927/python-kde3_3.15.2%2B20060422-2ubuntu4.1.debdiff
http://librarian.launchpad.net/6563656/adept_2.1.1ubuntu3.1.debdiff

TODO list:
- get a general 'yes, we want this in edgy and will put some serious time into it for testing' approval from the Kubuntu community and from release team.
- (extensive testing should be done with -proposed, not right now yet)

Accepted into edgy-proposed.

TODO list:

- Get explicit confirmation from mdz and the Kubuntu community that we really, really want this feature for edgy already, at the risk of breaking existing applications.
- Get written feedback (as bug comments) from at least 10 different testers (using different languages, mirrors, a local mirror, etc.) that these changes do not break the existing functionality of adept, correctly upgrade edgy to Feisty (modulo Feisty package bugs, of course), and other KDE applications (C++ and Python ones).

This comment is from a fairly inexperienced linux user (sometimes good to see if the novice can make it work). I am running Edgy 2.6.17-11-386 on AMD64 Turion, using KDE 4:3.5.6-0ubuntu1~edgy1 packages. I followed directions located in WIKI https://wiki.ubuntu.com/KubuntuDistUpgrade to the letter. Adept updated two of the KDE packages; however, the package kdelibs reports a BREAK (UPGRADE) error when trying to upgrade 4:3.5.6-0ubuntu1~edgy1 to 4:3.5.6-0ubuntu7~edgy1. The details tab shows kdelibs4c2a >= 4:3.5.6-0ubuntu1~edgy1 appearing in black. I went to the website http://kubuntu.org/~jriddell/tmp/edgy-dist-upgrade-kde356/ and noted that the version of kdelibs4c2a is an AMD64 version.

The Adept manager did flash the various screens advising of a distribution upgrade available and did download the upgrade program; however, the program did not execute, neither before closing Adept, nor after closing Adept. I presently have Adept Notifier sitting in system tray notifying me of the kdelibs library (the broken package) to upgrade. Adept flashes the screeens and redownloads the upgrade program after each execution of the "apply" button, despite the fact that not all of the packages updated beforehand. I am assuming that if the proper kdelibs4c2a library were loaded in Jonathon Riddle's directory, it might work--I am really stretching my knowledge in making this assumption.

I hope this outside feedback helps. I hear many good things about Feisty that will fix several annoyances that I have contended with last 6 months with Dapper and Edgy and am looking forward to its stable release.

Larry

Edgy with kde3.5.6 repository enabled. I also have a few other non-standard repos. I'm including my sources.list just in case it matters.

After updating the repositories the changelog was shown and the upgrade program downloaded. But it was not executed.
This was adept-managers terminal output:

gpg:
Signature made vr 09 mrt 2007 23:21:56 CET using DSA key ID 437D05B5
gpg:
Good signature from "Ubuntu Archive Automatic Signing Key <email address hidden>"

gpg:
WARNING: This key is not certified with a trusted signature!
gpg:
         There is no indication that the signature belongs to the owner.
Primary key fingerprint:
 6302
 39CC
 130E
 1A7F
 D81A

 27B1
 4097
 6EAF
 437D
 05B5

can't find DistUpgradeViewKDE

I did not think of running Adept in the terminal. I did this time and can confirm the same GPG outputs that Bart Cerneels spoke of in the previous post.

The first time I tried this, the Upgrade Wizard showed.

The gpg error shown above appeared while navigating to the last tab in the Upgrade Wizard. Clicking on Finish then had the "can't find DistUpgradeViewKDE" shown in the terminal.

I confirm the last three posts. Also adept proposes to update kdelibs but in the end doesn't do anything as the upgrade would break the install. Any suggestions on how to overcome this?

Downloaded the latest just now, and tried again.

Clicked "Fetch Updates"
  - some file is copied to my filesystem
  - Upgrade Wizard pops up.
  - Click "Next" to get to the release announcement
  - Click "Next"
  - Downloading and verifying upgrade tool, gets the following terminal output:

gpg: Signature made Tue 13 Mar 2007 04:29:32 NZDT using DSA key ID 437D05B5
gpg: Good signature from "Ubuntu Archive Automatic Signing Key <email address hidden>"

gpg:
WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint:
 6302
 39CC
 130E
 1A7F
 D81A
  27B1
 4097
 6EAF
 437D
 05B5

  - despite this, it shows "Ready to upgrade..."
  - Click "Finish", nothing happens, and gets the following terminal output:

can't load DistUpgradeViewKDE
error: /usr/lib/python2.4/site-packages/kparts.so: undefined symbol: _ZN11konsolePart8setPtyFdEi

Traceback (most recent call last):
  File "/tmp/kde-root/adept_managerypLMZa.tmp-extract/dist-upgrade.py", line 48, in ?
    app.run()
  File "/tmp/kde-root/adept_managerypLMZa.tmp-extract/DistUpgradeControler.py", line 839, in run
    self.fullUpgrade()
  File "/tmp/kde-root/adept_managerypLMZa.tmp-extract/DistUpgradeControler.py", line 821, in fullUpgrade
    if not self.doDistUpgrade():
  File "/tmp/kde-root/adept_managerypLMZa.tmp-extract/DistUpgradeControler.py", line 534, in doDistUpgrade
    res = self.cache.commit(fprogress,iprogress)
  File "/usr/lib/python2.4/site-packages/apt/cache.py", line 204, in commit
    res = self.installArchives(pm, installProgress)
  File "/usr/lib/python2.4/site-packages/apt/cache.py", line 179, in installArchives
    res = installProgress.run(pm)
  File "/usr/lib/python2.4/site-packages/apt/progress.py", line 217, in run
    res = self.waitChild()
  File "/tmp/kde-root/adept_managerypLMZa.tmp-extract/DistUpgradeViewKDE.py", line 259, in waitChild
    self.updateInterface()
  File "/tmp/kde-root/adept_managerypLMZa.tmp-extract/DistUpgradeViewKDE.py", line 283, in updateInterface
    self.parent.konsole_frame.show()
AttributeError: 'DistUpgradeViewKDE' object has no attribute 'konsole_frame'

- After the first crash I did:
dpkg --configure -a
apt-get -f install

and started the adept_manager again
The upgrade tool crashed after a while, I think both crashes are related with update or the ssh packages.

Traceback (most recent call last):
  File "/tmp/kde-root/adept_managerFdomoa.tmp-extract/dist-upgrade.py", line 48, in <module>
    app.run()
  File "/tmp/kde-root/adept_managerFdomoa.tmp-extract/DistUpgradeControler.py", line 839, in run
    self.fullUpgrade()
  File "/tmp/kde-root/adept_managerFdomoa.tmp-extract/DistUpgradeControler.py", line 821, in fullUpgrade
    if not self.doDistUpgrade():
  File "/tmp/kde-root/adept_managerFdomoa.tmp-extract/DistUpgradeControler.py", line 534, in doDistUpgrade
    res = self.cache.commit(fprogress,iprogress)
  File "/usr/lib/python2.5/site-packages/apt/cache.py", line 204, in commit
    if res == pm.ResultCompleted:
  File "/usr/lib/python2.5/site-packages/apt/cache.py", line 179, in installArchives
    installProgress.finishUpdate()
  File "/usr/lib/python2.5/site-packages/apt/progress.py", line 217, in run
    os._exit(res)
  File "/tmp/kde-root/adept_managerFdomoa.tmp-extract/DistUpgradeViewKDE.py", line 259, in waitChild
    self.updateInterface()
  File "/tmp/kde-root/adept_managerFdomoa.tmp-extract/DistUpgradeViewKDE.py", line 283, in updateInterface
    self.parent.konsole_frame.show()
AttributeError: 'DistUpgradeViewKDE' object has no attribute 'konsole_frame'

No problems, errors, and breakages from my system even after multiple reboots and multiple app relaunch using various applications. The patches and upgrades seems to be working well. Will give updates if I encounter any problems.
(Edgy on Intel D845EPI/512MB/Celeron 2.7G)

The output you have all mentioned from GPG is not an error - it signifies that GPG has verified the integrity of the downloaded archive (meaning the archive is not corrupt). The Kubuntu-Upgrader wizard will _not_ continue if GPG returns an error (if GPG cannot verify the archive against the signature, in the case that the archive is corrupt).

Lafa: I have fixed that crash, please try again.

Users of 3.5.6 packages: please use this new archive instead for i386 "deb https://wiki.kubuntu.org/KubuntuDistUpgrade /.", the kdelibs version is smaller so you will need to download the package directly "wget http://kubuntu.org/~jriddell/tmp/archive-edgy-dist-upgrade-kde356-i386/kdelibs4c2a_3.5.6-0ubuntu7really3.5.5_i386.deb http://kubuntu.org/~jriddell/tmp/archive-edgy-dist-upgrade-kde356-i386/kdelibs-data_3.5.6-0ubuntu7really3.5.5_all.deb; dpkg --install kdelibs4c2a_3.5.6-0ubuntu7really3.5.5_i386.deb kdelibs-data_3.5.6-0ubuntu7really3.5.5_all.deb"

Now the upgrader starts and seems to work fine. I don't get any output in the (hidden) terminal window though. This warning was printed to the terminal:
kdecore (KProcess): WARNING: setPty()
kdecore (KProcess): WARNING: _attachPty() 13

I tried closing the updater and restarting to see how it would react. Since the download process can take a very long time I guess this will happen often.

Current behavior:
   When starting adept_manager again the updater didn't run automatically, but it did after pressing fetch again. Updater doesn't seem to like being run again
Expected behavior:
adept_manager spawns upgrader as long as it update is not complete or KDE reminds the user to finish updating after start-up.

I followed the instructions on the wiki, added the extra repo because I had 3.5.6, it all went ok and finished the upgrade.

It told me it was disabling some 3rd party sources and it did.

There were some prompts in the built in terminal that I had to hit enter for [MORE] and for it to proceed. This happened twice I think and there wasn't really any indication that it wanted you to hit enter but that's pretty typical for stuff in the terminal. One was libssl and the other was related to multi disk raid arrays and after the [MORE] prompts asked me what I wanted to do wanting a Y or N.

The prompts that showed the diffs of files that were changing worked good.

It did say something crashed at the end but there was no error message and I just closed it and it continued on and it prompted for the restart and it did restart.

Very nice and it seems to work really good.

I used this tool to upgrade and it worked really nice, there is an encoding issue in the dutch parts of the translation, but those are very minor. The tool needs tweaking here and there, but overall it is ok.

I especially like the very intuitive diffs where there are conflicts. I will use the tool as is on more computers and recommend it to others.

AMD64x2 running fresh i386 edgy

failed at this point

61.7021:Preparing ttf-bengali-fonts

apt.log attached. main.log to follow below

and the apt.log for the above failure.

and the apt.log for the above failure.

Worked perfectly on a fresh install of edgy on an ASUS M6B. Great tool.

Worked fine in a VMware install.

I just did a 'dist upgrade' from Kubuntu Edgy to Feisty using the new upgrade tool that people have been asked to test. It took about an hour and a half but aside from that everything went ok. I have to use the openchrome drivers for my video so had to do
'sudo dpkg-reconfigure -phigh xserver-xorg'
in recovery mode on my first boot into Feisty in order to select the Vesa driver because ' /etc/X11/xorg.conf' had been written anew and had reverted to naming the Vesa generic driver. I expected that would hapen though. Once I had managed to log in graphically I reinstalled the Openchrome driver, amended xserver-xorg and /etcX11/xorg.conf, restarted X and got back into Kubuntu.
Nothing seems to have been lost by way of my settings. All of the app windows are opening where I had set them to in Edgy, my custom icons are still loaded, windows are the same as in Edgy. It looks like all went ok. I can't see any missing files in my /home partition.
I am impressed really. This is the first dist-upgrade I have done. I only started using Kubuntu about 6 months ago so I am a newb to Linux.
Good stuff.
I am a happy customer.

dkaddict

I just finished the update on my desktop computer, and I had some problems.

The update tool crashed on Samba's update. I made a

dpkg --configure -a

witch worked well, followed by a

apt-get -f install

who had to update two packages :

Les paquets supplémentaires suivants seront installés :
  kubuntu-docs samba
Les paquets suivants seront mis à jour :
  kubuntu-docs samba

after that, I made an apt-get update && apt-get upgrade

Now everythings semms ok and up to date.

I attach the apt.log on this message and main.log on the next one.

the main.log

Worked great for me :)
I had some issues getting it to work as adept didn't like my cut and paste. Worked fine once i cut and paste straight into the sources.list Minus the [WWW]. Might be worth putting the repositories in a code box to remove this [WWW] thing so people can cut and paste.
Some minor issues for me when i was near finished and it listen now unsupported packages i wanted to keep the old Linux kernel as its always best to keep a possible backup plan until things test out. I've had to boot an old kernel before today after an upgrade. I didn't want to keep some older libs wlassassistant (or whatever the correct name is) and option to differentiate between unsupported and no longer wanted vs unsupported and wanted would be good.
Also knetwork manger seems to do nothing but thats more a Fiesty bug than this upgrade (i think/hope). I click and no response.
lastly i cant confirm exactly where i think after i added the repository but before it let me upgrade i had to jump in the command line and do a "dpkg --configure -a" as everything went pear shaped and i couldn't open Adept anymore. I think it was after the fetch updates.
Adept automatically closed when the upgrade started so at least for me this bug is either fixed or happy with my setup.

Overall this is very close to ready for mainstream use other than the odd minor issue.

I seem to have run into some brain damage on my end but in doing so recognized that some slightly more descriptive documentation could help avoid this for other users. I am a long time Debian user and have recently decided to try out Kubuntu for a couple reasons I wont go into here, leave it to say I know my way around.

I found directions at https://wiki.kubuntu.org/KubuntuDistUpgrade and read all the way through them before starting. The *Important:* note at the bottom actually threw me off. I read it as meaning that Adept would have to be quit after Adept had started Fetching Updates, understandably a boneheaded move now that the upgrade failed in a variety of ways but perhaps not an uncommon mistake. As such I would propose that the *Important:* message be changed from:

Important: there is a bug in the tool, you need to quit Adept after it has started.

to:

Important: there is a bug in the dist-upgrade tool, you need to quit Adept after the dist-upgrade tool has started.

Perhaps this is exact to the point of being redundant but it would have saved me trouble within my first 24 hours of running Ubuntu.

-i

One glitch: the acpid didn't finish its setup because

acpid: can't open /proc/acpi/event: Device or resource busy

I just edited /var/lib/dpkg/status and manually set the package's status to "install ok installed," then ran "dpkg --configure -a" and the packages which depended on acpid (acpi-support, powermanagement-interface, kubuntu-desktop) configured correctly.

It told me that "third part sources" were disabled. Then it told me my system was up-to-date, even though I hadn't installed any Feisty packages.

So, it didn't work for me.

Sorry, I should add that I was doing this in a chroot environment.

did not work on PPC 64

i followed the instructions on /KubuntuDistUpgrade and nothing happened. i was not prompted by any screen asking me if i wanted to upgrade.

the machine is an iMac G5 rev 1 PPC 64 running Edgy. hope this is helpful.

> It told me that "third party sources" were disabled. Then it told me my system
> was up-to-date, even though I hadn't installed any Feisty packages.
>
> So, it didn't work for me.

Ditto, sadly.

Worked fine on my home installation. Only mild complaint is that after having upgraded to 7.04, Adept Updater always says 'A new version of Kubuntu is available! Click next...' after installing any patches. the Next button is greyed out but it is a bit misleading.

Did not work at all on my office installation. I suspect that this is because it is behind a proxy. I have set a http_proxy environment variable, and have proxy lines in apt.conf. Normally Adept works fine. But after following the instructions (https://wiki.kubuntu.org/KubuntuDistUpgrade) the box offering the upgrade to 7.04 did not appear.

Upgrade from KDE 3.5.6 went well here... Except setting new repositories. I used local mirror in Cesnet (czech academic network) (yes, i know we have other mirrors in cze...) and there are no feisty repositories yet. I think, in this case, it's better to contact the main ubuntu repositories (or let the user to choose from mirror list) and eventually use what was found. Only if it's not successful show the message that something is wrong and stop upgrade process. At the end, the dialog with message containing "While scanning your repository no mirror entry for the upgrade was found." ... should use word wrapping ;)

Same as Graham Hawkins, started Feisty from clod boot, Adept Updater notices a "new version of Kubuntu is available. Please click Next" In the Updater there is no "Next" button. Closed that. Started Adept Manager. "Fetch Updates" and "Version Upgrade" blue button appears. Click and dist-upgrade tool starts and says," A new distribution version is available! Click netxt if you wish to upgrade now." Click and "Error! Could not download the release announcement. Please check that your Internet connection is active." Obviously, it is as Fetch Updates worked. Then tried in CLI "sudo apt-get dist-upgrade" just to make sure and nothing...All is already updated.

I first updated my Dutch Edgy install (KDE 3.5.5).
Then enabled edgy-proposed as stated in the wiki.
Fetched all updates and installed them. (about 11 updates)
Closed adept-manager and restarted it. After fetching all updates it did not offer me to upgrade to Feisty at all,
Logging out and restarting X-Window and KDE did not help. Even rebooting did not help.
Tried changing the gb mirror to the nl mirror, still no luck.
Edgy is however still running without problems...

I first updated my Edgy install.
 Then enabled edgy-proposed as stated in the wiki.
 Fetched all updates and installed them.
 Closed adept-manager and restarted it. After fetching all updates it did not offer me to upgrade to Feisty at all,
 Logging out back did not help.
 Edgy is however still running without problems...

So, it did not work.

I first updated my german Edgy install (KDE 3.5.5).
Then enabled edgy-proposed as stated in the wiki.
Fetched all updates and installed them (about 11 updates).
Closed adept-manager and restarted it. After fetching all updates it did not offer me to upgrade to Feisty at all, though a new window popped open but closed before I could read the contents. Window opens reproducibly when ffetching updates.
Rebooting did not help.
Edgy is however still running without problems ...

It seems the wizard to update to Feisty only get's run when an actual package is being upgraded on Edgy, otherwise it is not run.

Adding on what I already said. It would be nice if you offer a way to run the update wizard without needing a package to be upgraded. I have the lattest packages of all repositories including edgy-proposed and now I cannot run the wizard (when the wizard run I didn't have time to upgrade, so I cancel it).

Same problem for me as for rkelly, Jisao and Stefan Gründel.

Same problem for me, on a VMware install tho, but there was another guy who had it working on a VMware

Here are a few things that happened during my upgrade from Edgy to Feisty. In general, there were some buggy/broken php.ini replacement handling, buggy /etc/modprobe.d/blacklist handling, and a loss of X after reboot for my NVIDIA GeForce4 4200 Go. I love Kubuntu, but the upgrade to Feisty wasn't as smooth as I hoped. I understand it is still in beta, so the details of my problems are mentioned here:

1. PHP
During Fetching and installing the upgrades, it was at about 63% and I received the following prompt:
Configuring php5-cli:
A new version of configuration file /etc/php5/cli/php.ini is
available, but your version has been locally modified.

  - install the package maintainer's version
  - keep your currently-installed version
  - show the differences between the versions
  - show a side-by-side difference between the versions
  - start a new shell to examine the situation

What would you like to do about php.ini?

When I picked option 4, there was a long delay (a minute?) before the comparison started. I expected kompare or something that is more easily followed than a standard diff. Once the MORE prompts started, I didn't know how to stop the differences to pick another method out of fear of killing the whole upgrade.

I then picked option 5 and received the following error:
        /usr/bin/ucf: line 954: /dev/tty: No such device or address

Suggestions...
- Make the shell work.
- Have a way to exit the diff.
- Have a MORE prompt that allows more options such as quit. php.ini is a large text file, so a diff is virtually useless for many people.
- Option 5 makes no sense if there is no way to look at the php.ini file that is going to be installed (since the file name isn't given) to do any comparison on my own.
- It'd be nice if there was a way to have some of these questions not halt the whole process. Perhaps rename the old php.ini and install the new one, or install the new one as php.ini.newversion and then ask this question at the end of the upgrade.
- Have an option to rename existing and install one from package.
----------------------------------------------------
2. busybox-initramfs
- At Fetching and installing the upgrades: 68%... Installed busybox-initramfs and warning to keep or replace /etc/modprobe.d/blacklist.
- Noticed that in this case you have /etc/modprobe.d/blacklist.dpkg-new, which make more sense than how PHP was handled. It was easier for me to do a kompare or something on my own at the command prompt.
- Noted that it was handled differently than php.ini because it wasn't a menu of options in a text window. This was
an actual GUI screen with a diff already done for me.
- The "SHOW DIFFERENCE >>>" does nothing. The difference was already in a visible textbox.
----------------------------------------------------
3. libapaache2-mod-php5
- Got the following message:
Setting up libapache2-mod-php5 (5.2.1-0ubuntu1) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend...

Update-Manager, DistUpgrade, No prompt to upgrade

Followed this wiki: https://wiki.kubuntu.org/KubuntuDistUpgrade
Did notice it changed from the last time I followed this for test system 1.
Followed it as written for test system 2.
All goes well except I never get the prompt that there is an upgrade to 7.04.
I receive no errors. I start update-manager from terminal and no errors there either.
Don't really think this a bug, but could be wrong there.

Is there a way to force the Upgrade Wizard to run and report any errors?

I have the same problem as (https://launchpad.net/ubuntu/+source/update-manager/+bug/84717/comments/244) above.

I don't get the prompt as it was mentioned on the wiki page.

I was running: KDE 3.5.5 with boat loads of extra repositories, which did not show up in Adept (i like to maintain extra repositories in /etc/apt/sources.d/*.list).

Anyways, I was able to upgrade my machine to Feisty manually without any issues.

I think that this can be a good solution for upgrade the system.
I've installed it on feisty system with no problems (but at upgrade request is displayed a wrong message of 'no internet connection active' (see attachment).
On next week (if possible) i've try to test it on a edgy system.
I hope that can be easier to have a only 'one buttun action' to upgrade the system:
all (beginners) users don't have to modyfy/add any line of repositories. Only one icon have to be pressed to update the system.
I've think that this icon/button have to be placed also on the appplication menu and/or on the desktop.

tried to follow instructions but did work!

Hi,

1. I followed the instructions on this page:

https://wiki.kubuntu.org/KubuntuDistUpgrade

2. I quit Adept Manager, and restarted it as follows:

sudo adept_manager

3. After restarting, I clicked 'Fetch Updates'. The console showed the following messages:

Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Link points to "/tmp/kde-root"
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
kded: cannot connect to X server :0
DCOP aborting call from 'anonymous-32388' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
kapture::PkgSystem::PkgSystem()
python
python-support
python
python
python-support
python
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
kio_uiserver: cannot connect to X server :0.0
DCOP aborting call from 'adept_manager-32375' to 'kio_uiserver'
python
python-support
python
ERROR: KUniqueApplication: Registering failed!
ERROR: Communication problem with kio_uiserver, it probably crashed.
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
kio_http_debug: WARNING: (32418) Can't communicate with kded_kcookiejar!
kio (kioslave): WARNING: Can't communicate with kded_kpasswdserver!
python
python-support
python

4. Nothing else happened.

I was under the impression that I would be presented with an upgrade tool. However, no such tool appeared.

After following the instructions here:

https://wiki.kubuntu.org/KubuntuDistUpgrade

Since nothing happened, I decided to upgrade to 3.5.6. The upgrade was successful, so I decided to try the steps again.

I added the following line, verbatim, to the Adept Manager (after starting it from the system menu, not console):

deb http://kubuntu.org/~jriddell/tmp/archive-edgy-dist-upgrade-kde356-i386/ ./

This appeared to put in corrupted data. I proceeded anyway. Adept Manager crashed in flames. The next time I started it, it complained of a corrupted line in /etc/apt/sources.list.

I then removed the offending line from the file and ran apt-get update. I was greeted with:

Reading package lists... Done
W: GPG error: http://kubuntu.org edgy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A506E6D4DD4D5088
W: You may want to run apt-get update to correct these problems

I re-ran apt-get update and continued to receive the same error message.

I then repeated the steps listed in this message and have attached a screenshot that shows the corrupted string data within Adept Manager.

URGENT!!!
Okay, all is working fine with a couple of exceptions so far:

Cannot adjust Date & Time either from the system tray or from system settings. I get an error that says, "Su returned with an error".
This is a really bad bug and really cannot understand how this would have changed unless some automated diff operation when bad.

Please fix this.

Disregard that last outburst. Somehow had a bad login. Maybe due to bad logoff rather than restart.

Rebooted and all is well in Kubuntu land again.

Bruce

After my previous problems I reinstalled Kubuntu 6.10 and attempted this update again following the instructions at https://wiki.kubuntu.org/KubuntuDistUpgrade. This seemed to work fine until after step 10 no process started to do the update. I did see the following error in a console i had previously started adept_manager from to overcome a problem with kdesu though I had started it from the K-Menu for this process.

kio_http_debug: WARNING: (20271) Can't communicate with kded_kcookiejar!
kio (kioslave): WARNING: Can't communicate with kded_kpasswdserver!

Ian

I followed the instructions at https://wiki.kubuntu.org/KubuntuDistUpgrade and as the previous post, nothing happened after step 10. I then rebooted and adept came up with only 2 choices, fetch updates and preview. I tried the fetch updates and it appeared to be checking the repositories but when it was finished I had no choices available other than fetch updates and preview. I tried adding the repository again and still the same results.

Unfortunately, after following instructions, adept-manager does not offer any upgrades of Kubuntu -- apparently the same situation as described above. Is there any way to invoke it manually?

I followed the instructions found at: https://wiki.kubuntu.org/KubuntuDistUpgrade

After the final "Fetch Updates" just nothing happens.
I tried using the suggested workaround "xhost +root" but the only result I get is an error message: "xhost: bad hostname "root""

I'm using Edgy with KDE 3.5.5

I followed the instructions at KubuntuDistUpgrade on a fresh installation of Edgy and nothing happened past step 10. I tried previously on an installation of Edgy with KDE 3.5.6 and nothing happened then either. I am going to try a manual upgrade. Rather annoying as neither the standard nor the alternate beta CD would work for me - both hang towards the end of the installation.

Nothing happened past step 10 for me to in Kubuntu.
I did the following to make it work in kubuntu:
1. Installed update-manager via adept (it was not installed in kubuntu, since it is a gnome tool)
2.Ran update-manager -d and followed the instructions

I found the steps here: https://help.ubuntu.com/community/FeistyUpgrades and followed step "Beta upgrade"

This worked like a charm

So it seems like the new Kubuntu Dist Upgrade tool does not work like it should.

Thanks for all the testing, this bug is now closed. See https://help.ubuntu.com/community/FeistyUpgrades for how to upgrade. Please report further problems in new bugs.