Kubuntu update-manager for Upgrade from Edgy to Feisty does not show error when aborting

[Monika Eggers]

- adept_notifier shows updates waiting (with the exclamation mark in the triangle)
- I click on it, enter password, adept_updater starts
- click on "fetch lists of updates"
- click on "apply changes"
- a new window "Upgrade Wizard" comes up, I click on "next"
- Kubuntu Release Announcement about Feisty Fawn, I click on "next"
- something downloads, "Ready to upgrade", I click on "finish"
- the "Upgrade Wizard" closes, then nothing happens, no error message, so I eventually close adept_updater

So, to get error messages, I started adept_updater from a terminal, and do everything the same way as above. The output is attached. The first error message is
"can't load DistUpgradeViewKDE (/usr/lib/python2.4/site-packages/kparts.so: undefined symbol: _ZN11konsolePart8setPtyFdEi)"
I suppose this is the reason why there is no GUI / no GUI error messages.

Later on it says I need 5589k free disk space in /usr, which I can't get.
(df -hl: /dev/.static/dev/hda3 9,1G 4,7G 4,0G 55% / ) So that seems to be the reason why it actually aborts and not a bug. The bug is that one doesn't get a visual error message when one starts update_manager the normal way (by clicking on the triangle icon).

[Monika Eggers (monikakrug)]

I just noticed something, it only asked for 5589k of free disk space, that's only about 5.5 MB (I misread that first and thought 5.5 GB, then it would be correct, I don't have 5.5 GB left). So that's a bug, too, then.

[Velek (velek)]

Seems to be fixed by some new kde packages, now it worked well for me.

[Richard Birnie (rbirnie-deactivatedaccount)]

Just following up on this bug. Is this still a problem or has it been resolved by some more recent updates. Velek says it works fine, Monika is this still a problem? If the error still exists and is reproducible then attaching the log files from /var/log/dist-upgrade if there are any following the error would be a big help in figuring out what causes this.

thanks,
Rich

[Monika Eggers (monikakrug)]

The problem still exists.

I tried it the same way described above, starting sudo adept_updater from the terminal, it starts the upgrade wizard for Feisty in the end.

On the first try it stopped when it got a 404 from one of the repositories in my sources.list. That error information and any progress information was only seen in the terminal window, no GUI. The output to the terminal window says "can't load DistUpgradeViewKDE" at some point. The sources.list is unchanged, i.e. still says edgy everywhere. I will attach the output as 404.log.

I then outcommented the offending repository from my sources.list (isn't the upgrade wizard supposed to do this?) and tried again.

It stops at some point with a message in the terminal like: "Asking for confirmation ... Do you really wish to continue? This will last some hours and the upgrade process cannot be interrupted." This output and all other output and progress information is again only seen in the terminal window, there is no GUI. Again just the Adept Updater sitting there with it's "Beenden" (Close) button. The output again says "can't load DistUpgradeViewKDE" at some point. I will attach that output as second.log. The sources.list is at this point changed to feisty already.

I will also attach the apt.log and main.log from /var/log/dist-upgrade as they were at the time after the second run.

[Monika Eggers (monikakrug)]

And something weird happens afterwards: In the terminal window from which I started "sudo adept_updater", after ending the attempt to upgrade to Feisty, error and debug messages will be shown for other KDE programs, e.g. kate, as if I had started kate from that terminal, even though I started it the normal way from the K-menu.

[Richard Birnie (rbirnie-deactivatedaccount)]

Monika,

Thanks for your efforts in tracking down this problem. I'm afraid I can't tell you how to solve the problem (sorry) but we have enough information now for the developers to take a look and try to find out what is wrong.

thanks again for helping to improve Kubuntu.

[Rolf Leggewie (r0lf)]

Did this error ever reoccur during one of the later releases?

[Monika Eggers (monikakrug)]

Now, I did not run into such problems during later upgrades.

[Jean-Baptiste Lallement (jibel)]

Thanks for following up. I'm closing this report due to your last comment.
Don't hesitate to submit any new bug.