Grub 1.97beta4 fails to set up correct Windows XP entry

Bug #466434 reported by Bruce R
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: grub

In installing 29oct2009 release, 64-bit Karmic, the new grub 1.97beta4 failed to correctly detect and create a new startup menu for one of two WinXP active partitions. Two menu entries were created in /boot/grub/grub.cfg but both contain the same the same UUID code, so only that partition can be loaded. For many years 'Legacy GRUB' has worked well, with gedit or even grubedit tools allowing more meaningful menu display and operation, but I suppose that's what you must expect from a Beta4 version.

If it can't be fixed very soon, an Update reversion to 'Legacy Grub' might be a possible solution, to encourage migration from dual-boot Windows ?

ProblemType: Bug
Architecture: amd64
Date: Sat Oct 31 11:08:30 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
LiveMediaBuild: Debian GNU/Linux 5.0.1 "Lenny" - Official Snapshot i386 LIVE Binary 20091005-14:14
NonfreeKernelModules: nvidia
Package: grub (not installed)
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: grub
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1994): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1994): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2095): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2090): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:2089): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -10 and height 24

Revision history for this message
Colin Watson (cjwatson) wrote : Re: [Bug 466434] [NEW] Grub 1.97beta4 fails to set up correct Windows XP entry

On Sat, Oct 31, 2009 at 11:24:45AM -0000, Bruce R wrote:
> In installing 29oct2009 release, 64-bit Karmic, the new grub 1.97beta4
> failed to correctly detect and create a new startup menu for one of two
> WinXP active partitions. Two menu entries were created in
> /boot/grub/grub.cfg but both contain the same the same UUID code, so
> only that partition can be loaded.

Could you please show the output of 'sudo os-prober'?

> If it can't be fixed very soon, an Update reversion to 'Legacy Grub'
> might be a possible solution, to encourage migration from dual-boot
> Windows ?

We aren't going to go back; GRUB Legacy was unmaintained and had a whole
different set of more or less unfixable bugs. At least the bugs in GRUB
2 show prospect of being fixable. :-)

affects: grub (Ubuntu) → grub2 (Ubuntu)
Revision history for this message
Bruce R (bm007a0030) wrote :

Understood Colin, thank you for the explanation.

'sudo os-prober' returns

'/dev/sda2:Microsoft Windows XP Home Edition:Windows:chain
 /dev/sda3:Microsoft Windows XP Home Edition:Windows1:chain
 /dev/sdb1:Windows 7 (loader):Windows2:chain'

The first XP Home is a online version, undergoing the usual MS update update and tinkering process, whilst the second is an unmodified, simple offline clone used for occasional uninterrupted and largely unattended tasks like disc burning, This arrangement of different choice boot up sessions has served me well using Legacy GRUB and its controlling, easily modified 'menu.lst', but the read-only 'grub.cfg' has me puzzled and I haven't yet found any documentation for the new GRUB.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Apologies for the delay in response, we get more reports than we have manpower to work on.

Did this ever occur in lucid or later?

Changed in grub2 (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: New → Incomplete
Revision history for this message
Bruce R (bm007a0030) wrote : Re: [Bug 466434] Re: Grub 1.97beta4 fails to set up correct Windows XPentry

Yes, this occurs with ALL subsequent versions of Ubuntu using 'grub2' but
I have circumvented this by reverting to 'legacy grub' which is far easier to
customize, with a very useful 'timeout -1' capability in 'menu.lst' that yields
a startup menu indefinite pause that allows consideration of what to select.

Thankfully 'legacy grub' hasn't yet been deleted from the repository but I
guess that its days are numbered.

I hope that this answers your question.
  ----- Original Message -----
  From: Rolf Leggewie
  To: <email address hidden>
  Sent: Saturday, August 13, 2011 4:15 PM
  Subject: [Bug 466434] Re: Grub 1.97beta4 fails to set up correct Windows XPentry

  Apologies for the delay in response, we get more reports than we have
  manpower to work on.

  Did this ever occur in lucid or later?

  ** Changed in: grub2 (Ubuntu)
         Status: New => Incomplete

  ** Changed in: grub2 (Ubuntu)
       Assignee: (unassigned) => Rolf Leggewie (r0lf)

  --
  You received this bug notification because you are subscribed to the bug
  report.
  https://bugs.launchpad.net/bugs/466434

  Title:
    Grub 1.97beta4 fails to set up correct Windows XP entry

  To manage notifications about this bug go to:
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/466434/+subscriptions

Rolf Leggewie (r0lf)
Changed in grub2 (Ubuntu):
assignee: Rolf Leggewie (r0lf) → nobody
status: Incomplete → New
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in grub2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]

Changed in grub2 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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