Public bug reported:
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: ubuntu
Importance: Undecided
Status: New
** Description changed:
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 console 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.
+ 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.
--
Upgrade from Dapper requires manual intervention
https://bugs.launchpad.net/bugs/223226
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
