Karmic -> Lucid upgrade fails with "Found linux image: /boot/vmlinuz-2.6.32-19-generic" when attempting to upgrade memtest86+
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lupin (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: update-manager
Hi folks, I'm attempting to upgrade my fully-up-to-date 9.10 Karmic installation to 10.4 Lucid beta1 using the GUI update-manager. Unfortunately, the upgrade has hit a snag when attempting to install the memtest86+ package.
1. What you expected to happen?
I expected the memtest86+ package to install normally and the appropriate GRUB entry to be updated to reflect the new package.
2. What actually happened?
The Distribution Upgrade terminal continually scrolls "Found linux image: /boot/vmlinuz-
3. The minimal series of steps necessary to make it happen, where step 1 is "start the program"?
a. In accordance with the instructions at http://
b. During step 4, "Installing the upgrades", update-manager attempted to upgrade the memtest86+ package.
c. The attempt to upgrade memtest86+ caused the distribution upgrade to stall with "Found linux image: /boot/vmlinuz-
d. Pressing ctrl-c in the Distribution Upgrade window's terminal results in a warning, saying that proceeding with skipping the package will result in a possibly-unusable system.
e. Opting to skip the package and continue the upgrade appears to be proceeding normally. (The upgrade is still in process. I will update this bug as needed.) At the time of this writing, I do not know what effect skipping memtest86+ will have on the rest of the upgrade, nor whether it'd be possible to install it properly after the upgrade.
If anyone requires additional information, I'd be happy to provide it.
Cheers!
-Pete
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 540579, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.