Thank you Colin Watson.
you are correct.
I thought I found a connection.
But most of my comments here should go
to synaptic/natty problems, bug #755694 -
Here is the real grub~1.99rc error:
sudo grub-editenv /boot/grub/grubenv unset recordfail
corrects the failure to count & automatically boot into natty.
However,
sudo grub-editenv /boot/grub/grubenv unset recordfail
only works once, the next reboot [restart] sets recordfail
back to problem mode.
it seems a lot like Bug #462888:
Bug Description
Binary package hint: grub2
Ubuntu 9.10 Karmic Koala beta
grub2~1.97-beta4-1ubuntu3
grub2 menu stays until I press enter.
grubenv reads: recordfail=1
My understanding is, that it should only read "1" if there was a boot
problem
or a "suspend / hibernate" problem.
The OS does put PC into "suspend" mode, & I can awaken it from there.
However, I have set "Never" mode for both PC & Monitor (in Power
Management),
so it should not put the PC into "suspend" in the first place.
But Grub2 apparently is told that the PC failed, because if I manually
put recordfail=0
it always changes back to recordfail=1, & thus the grub2 menu appears
indefinitely,
until I press enter.
I have devised a work-around that fixes the symptom but not the actual
bug:
by adding the following to the bottom of the /etc/grub.d/40_custom
script:
fi
if [ ${recordfail} = 1 ]; then
set timeout=3
else
set timeout=0
fi
# end
in this way if there was a problem with booting or suspend / hibernate
one has whatever timeout one adds to this script,
& if grubenv were set with recordfail=0 it would boot without delay.
As I wrote, it does not fix the actual bug, & perhaps it really is two
bugs.
one in ACPI managing, & the other in not resetting grub2 recordfail.
as to "Required input missing": I was unable to use the "Record a
problem..."
program, it refused to start, so I used: sudo ubuntu-bug grub2, to
report.
I could not find this exact bug described, so a new bug report may help.
I have attached grub.cfg, which of course shows the altered 40_custom. -
grub~1.99rc is not ready until recordfail is controlled by grub.
If there is a reason for grub2 not to automatically boot, it would
be helpful for grub to tell the user why, & what to do.
I am sorry for the grub/synaptic,natty mix-up, & for still not
knowing how to add more than one attachment at a time.
BavarianPH,
whether Unity or Gnome3,
please just leave me gnome-panel,
Main Menu & panel apps as an option.
Ubuntu Forever!
** Attachment added: "# GRUB Environment Block recordfail=1"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/755664/+attachment/2011638/+files/grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755664
Title:
grub 1.99~rc looses automatc count when synaptic freezes, and one has
to reboot to unfreeze natty-synaptic-package-manager.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
