Ubuntu
grub2 package

Multi-boot grub menu does not identify releases

Bug #1276544 reported by Richard Elkins on 2014-02-05

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	grub2 (Ubuntu)	Won't Fix	Medium	Unassigned

Bug Description

Ubiquity 2.10.29 does identify existing Ubuntu releases (E.g. "Trusty Tahr") during a potentital along-sideof Precise 12.04.04 type installation. However, this information is not reflected in the resulting boot menu.

For example, I shrunk Trusty from an entire disk installation to a 1/2 disk, leaving room for Precise 12.04.04. Then, I installed Precise along-side of Trusty. The attached 3 images are the resulting boot menu items on the display when the operator is prompted to select an image to boot from the grub menu.

"Windows" does show up in a dual boot case of Ubuntu with Windows. Why not include the Ubuntu release name+number for clarity?

Tags:

Revision history for this message

Richard Elkins (texadactyl) wrote on 2014-02-05:

3 images of the grub menu items of a multi-boot menu Edit (4.8 MiB, application/x-tar)

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2014-02-05:

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1276544

tags:

added: iso-testing

Colin Watson (cjwatson) on 2014-02-05

affects:

ubiquity (Ubuntu) → grub2 (Ubuntu)

Revision history for this message

Richard Elkins (texadactyl) wrote on 2014-02-05:

Apologies, Colin, I did not intend to contradict your change.

affects:	grub2 (Ubuntu) → ubiquity (Ubuntu)
affects:	ubiquity (Ubuntu) → grub2 (Ubuntu)

Brian Murray (brian-murray) on 2014-04-17

Changed in grub2 (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Richard Elkins (texadactyl) wrote on 2018-03-03:

This bug is over 4 years old. Is there any interest in fixing it?

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-03-07:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status:	New → Confirmed

Revision history for this message

Richard Elkins (texadactyl) wrote on 2020-10-12:

This is 6 years old. We need a "timed out" status! (-: Seriously, there is probably no interest as the world has moved on. I don't mind a "Wont Fix" status applied by whoever can do this.

Revision history for this message

Julian Andres Klode (juliank) wrote on 2020-10-12:

You can realistically only really have a single Ubuntu install per system anyway, otherwise it's mad ping-pong between bootloaders overriding each other (because there can only be one "ubuntu" bootloader). And newer bootloaders might not load older kernels or vice versa. OK, OK, what I say is valid only for EFI, but well, not much point doing much more work on os-prober for nicer BIOS support (and we need to kill it on UEFI anyway, and set BootNext from grub and use entry names from UEFI BootOrder, so that each foreign OS gets booted by rebooting to it, so that measurements and secure boot chain is correct).

Changed in grub2 (Ubuntu):
status:	Confirmed → Won't Fix

Revision history for this message

Richard Elkins (texadactyl) wrote on 2020-10-12:

wont Fix works for me, Julian.

At the time, I was running 2 Xubuntus because I had my personal stable and a non-virtual QA image. It would have been nice to have the boot menu state which is which by a more friendly name but I always guessed right by kernel version (QA was always higher).