Ubuntu
grub package

Fail to reboot the the correct image during the upgrade

Bug #47613 reported by Carlos Ribeiro
10
Affects Status Importance Assigned to Milestone
grub (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: update-manager

The upgrade process involves a reboot after the main installation is finished. It works fine if grub is with the default configuration - it will load the new image that comes with dapper. However, if 'grub' is configured to boot another image by default (for instance, the 'n-th' image in the list), the it will load the wrong image when rebooting.

Steps to reproduce:

1. Configure a Breezy system to boot some specific image ("default" directive in the /boot/grub/menu.lst file).

2. Run "update-manager -d". Wait until the reboot.

3. On the reboot, the wrong image will be loaded instead of the newly installed one.

Example: assume that you have 4 images in the original system, and that you are loading the 4th one. During the upgrade, the new image and the associated 'recovery mode' image will be added at the start of the list. After the reboot, the system will still load the 4th image - which is neither the original one, or the new one from Dapper.

Revision history for this message
Nathan Handler (nhandler) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in grub:
status: New → Incomplete
Revision history for this message
Carlos Ribeiro (carribeiro) wrote : Re: [Bug 47613] Re: Fail to reboot the the correct image during the upgrade

I don't know if it's an issue anymore, first because I found it in the
Breezy to Dapper transition - a long time ago as you said. Also, I only
update a few machines. But the fact is that I haven't had this issue in
recent versions of Ubuntu. It may be safe to close it by now.

On Thu, Aug 7, 2008 at 6:53 PM, Nathan Handler <email address hidden> wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in advance.
>
> ** Changed in: grub (Ubuntu)
> Status: New => Incomplete
>
> --
> Fail to reboot the the correct image during the upgrade
> https://bugs.launchpad.net/bugs/47613
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Carlos Ribeiro
Consultoria em Projetos
blog: http://rascunhosrotos.blogspot.com
blog: http://pythonnotes.blogspot.com
mail: <email address hidden>
mail: <email address hidden>

Revision history for this message
Nathan Handler (nhandler) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in grub:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.