[Bug 500832] Re: After update grub2 won't boot on its own
Launchpad Bug Tracker
500832 at bugs.launchpad.net
Tue May 5 05:30:59 UTC 2020
[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
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/500832
Title:
After update grub2 won't boot on its own
Status in grub2 package in Ubuntu:
Expired
Bug description:
After some karmic update (I guess) my eee 901 won't start on its own,
as it waits (for ever) for the user to select some boot option.This is
quite annoying as it was working ok before.
It could not be solved by touching the /etc/default/grub options.
Maybe pushing GRUB2 on karmic was a bad idea?
Too inmature?
Moreover when GRUB was working perfectly, it's easier to configure and more stable...
What does GRUB2 do that GRUB doesn't?
Why do we need GRUB2 anyway?
Just in order to have new bugs?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/500832/+subscriptions
More information about the foundations-bugs
mailing list