/etc/init.d/grub-common is not run after resume from hibernate. So it
cannot reset recordfail.
/etc/pm/sleep.d/10_grub-common also ist not run.
This is the reason why recordfail=1 in grubenv.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
That may be related too depending on the exact path the system takes;
but you said "after booting", in which case the init script is more
relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/447725
How about /etc/pm/sleep.d/10_grub-common ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/447725
Title:
grub nice 'recordfail' feature doesn't work for hibernation
To manage notifications about this
@Martin: /etc/init.d/grub-common (the grub-editenv call).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/447725
Title:
grub nice 'recordfail' feature doesn't work for hibernation
To manage notificat
This bug is still present in ubuntu 16.04.
What program is responsible for setting recordfail back to 0 after booting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/447725
Title:
grub nice 'recordfa
I confirm what Mike Clark says. Setting 'CONCURRENCY=shell' in
/etc/init.d/rc causes grub2 menu to be shown on every boot.
--
grub nice 'recordfail' feature doesn't work for hibernation
https://bugs.launchpad.net/bugs/447725
You received this bug notification because you are a member of Ubuntu
Bu
I realized the solution from bug report "Some essential services are not
started" at https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/500520
solved the issue about recordfail.
Have a nice day!
--
grub nice 'recordfail' feature doesn't work for hibernation
https://bugs.launchpad.net/bugs/4
I think I've figured out the root cause of the problem in Ubuntu 9.10,
upstart. I've found that on my system my default runlevel is 'unknown'.
When I init into a valid runlevel and restart, GRUB once again has a
timeout. Of course, that fix is only temporary as the system will once
again boot int
I am having the same bug, and recordfail=1 even if concurrency=none for
me. If I set recordfail=0 and restart grub works.. once. The next time
I restart it goes back to not using a timeout. I should note that I
never changed the concurrency setting at any time, it was always =none
for me.
--
g
concurrency=none is a work around, not a resolution. recordfail is still
set to 1 with concurrency=shell.
--
grub nice 'recordfail' feature doesn't work for hibernation
https://bugs.launchpad.net/bugs/447725
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I confirm what David Tomlin wrote.
After setting concurrency=none to concurrency=shell in /etc/init.d/rc
the file /boot/grub/grubenv has recordfail=1 after each reboot.
Resetting the line in /etc/init.d/rc to concurrency=none and one time
manual edit of /boot/grub/grubenv to change to recordfail=0
Just out of curiosity, did you happen to edit your /etc/init.d/rc file
and change concurrency=none to concurrency=shell? I did this because it
supposedly helps ubuntu boot faster by spreading the boot scripts across
two cores if you have a dual core processor. I had it set for weeks
before I expe
I confirm what BavarianPH said.
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Incomplete
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Fix Released
--
grub nice 'recordfail' feature doesn't work for hibernation
https://bugs.launchpad.net/bugs/447725
You received this
gksu gedit /etc/grub.d/40_custom
& add to the bottom:
fi
if [ ${recordfail} = 1 ]; then
set timeout=3
else
set timeout=0
fi
# end
this is a symptom fix, but also ensures that if there were a
real boot problem, one has 3 seconds (or whatever time)
to pick another option.
BavarianPH,
Ubunt
making grubenv read-only prevents the change to 1, is incorrect,
grub2 simply makes it a backup file & creates a new grubenv file with
recordfail=1.
so, if I want to boot directly to the O, I have to manally set grubenv
recordfail=0.
I hate to say it, but Grub-legacy was simpler, & less error pr
** Attachment added: "syslog.log"
http://launchpadlibrarian.net/34306932/syslog.log
--
grub nice 'recordfail' feature doesn't work for hibernation
https://bugs.launchpad.net/bugs/447725
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
recordfail=1 does not reset to 0
On my system, the latest updates changed grub2 settings to were
the menu appears regardless of changes in etc/default/grub script.
recordfail is set to 1, the grub menu appears and stays,
until I choose a selection, regardless of other grub2 settings.
only by c
This bug was fixed in the package grub2 - 1.97~beta4-1ubuntu1
---
grub2 (1.97~beta4-1ubuntu1) karmic; urgency=low
* Resynchronise with Debian. Remaining changes:
+ debian/default/grub:
- Adjust for default Ubuntu boot options.
- Use GRUB_CMDLINE_LINUX_DEFAULT option
** Changed in: grub2 (Ubuntu)
Status: New => Fix Committed
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
grub nice 'recordfail' feature doesn't work for hibernation
https://bugs.launchpad.net/bugs/447725
You received this bug notification because
I had fixed that for myself with this script (in /etc/pm/sleep.d/)
#!/bin/sh
# Tell grub that resume was succesfull
. "${PM_FUNCTIONS}"
case "$1" in
thaw)
grub-editenv /boot/grub/grubenv unset recordfail
;;
esac
--
grub nice 'recordfail' feature doesn
20 matches
Mail list logo
