[Bug 223226] [NEW] Upgrade from Dapper requires manual intervention
Launchpad Bug Tracker
223226 at bugs.launchpad.net
Mon Apr 28 07:48:35 UTC 2008
You have been subscribed to a public bug:
I just upgraded from Dapper to Hardy (Kubuntu) using the command-line
process described on the web site.
Several issues actually:
part-way into the upgrade, it tells me that kdm has to be manually shut down before it can proceed. Grrr! I'm running this in a root konsole window. That message should be in the procedure listed on the web, such as "Log out of KDE, and log into a root console session first". The good news is that after I accepted the option to abort, and I got myself to a text console, re-issuing the same update-manager -d command got it quickly going where it left off.
As it's proceeding, it tells me several times that I'll need to do something manually later. The first time, I think I can remember it, but soon the list of manual interventions gets too long for my memory, and I'm too lazy to transcribe all this stuff off the screen, so I believe there should be somewhere a log of all these upgrade messages stashed somewhere for later review, and the end of the upgrade process should present an option to print the list of manual interventions needed right after the reboot.
** Affects: kdebase (Ubuntu)
** Tags: dapper2hardy
Upgrade from Dapper requires manual intervention
You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu.
More information about the kubuntu-bugs