Release upgrade procedure "sucks" (from Gutsy to Hardy)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Invalid
|
Undecided
|
Rolf Leggewie |
Bug Description
Binary package hint: update-manager
I updated 3 computers from Ubuntu Gutsy to Ubuntu Hardy.
Using update-manager, within Gnome, as you "suggest" to do, it is an insane idea.
The first computers I did, I got everything crashing in Gnome crashes, everything was stuck, CPU was used new to 100%, and computer was very slow, since it definitively crashed the X session .... but that was obvious: it's like cutting the branch where you're sitting.
If you upgrade Gnome, running inside gnome it can't work (I imagine it would be the same with KDE)!
I think the concept behind this upgrade is completely wrong. You should force this kind of update outside gnome (for instance in the failsafe terminal session). you put a message: please logout, enter the failsafe session, and then type "sudo update-manager"
I updated the remaining 2 computers from fluxbox, and the upgrade proceeded smoothly! :o)
Even the idea of using pygtk is not the best one. If update-manager hangs, you can't restart it (at least before running: dpkg --configure -a, or before reinstalling python, depending where you update stopped).
I think you have to use some interface statically compiled, without any link to libraries.
cheers.
Thanks for your bugreport.
Please attach the files in /var/log/ dist-upgrade to this bugreport of the machine that crashed for you.
Thanks Michael