[Bug 1009531] Re: configuring grub-pc install devices did not work

2020-05-04 Thread Launchpad Bug Tracker
[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009531 T

[Bug 1009531] Re: configuring grub-pc install devices did not work

2020-03-05 Thread Marcus Tomlinson
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: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, w

[Bug 1009531] Re: configuring grub-pc install devices did not work

2012-10-07 Thread DrJohn
Grub menu, Ubuntu, and Win7 startups are normal. I didn't note in the previous post that running dpkg-reconfigure --frontend=gnome grub-pc did not change the output of debconf-show grub- pc. So, this looks like a mis-directed attempt by the package upgrade process to install Grub in the non-bootab

[Bug 1009531] Re: configuring grub-pc install devices did not work

2012-10-07 Thread DrJohn
Similar happened to me upon update manager upgrade to grub -pc 1.99-21ubuntu3.4. The "COnfigure Grub Devices" dialog offered choices of /dev/sda and /dev/sda6. Selecting both of these, the Details display of update manager showed /usr/sbin/grub-probe: error: cannot stat '/,' I deselected /dev/sda

[Bug 1009531] Re: configuring grub-pc install devices did not work

2012-06-08 Thread Steve Langasek
I saw this bug myself but assumed it had to do with my recent frankenstein brain swap (rsync-based install to a new hard drive in my laptop). If others are seeing it, I guess there's a real bug here. ** Changed in: grub2 (Ubuntu) Status: New => Confirmed ** Changed in: grub2 (Ubuntu) I