This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of U
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
I have the same issue under 14.04 LTS (amd64, fresh install). My
environment is:
root@PC:/etc/grub.d# dpkg -l | grep grub
ii grub-common 2.02~beta2-9ubuntu1
amd64GRand Unified Bootloader (common files)
ii grub-gfxpayload-lists
** Changed in: grub2 (Ubuntu)
Assignee: Colin Watson (cjwatson) => (unassigned)
** Changed in: grub2 (Ubuntu Karmic)
Assignee: Colin Watson (cjwatson) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/428570
Title:
Default grub2 configuration won't boot through to default OS
To mana
** Bug watch added: GNU Savannah Bug Tracker #33576
http://savannah.gnu.org/bugs/?33576
** Also affects: grub via
http://savannah.gnu.org/bugs/?33576
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Upstream comments are really interesting... they state that all of these
issues are caused by Ubuntu-specific patches.
BTW I tried to link the upstream bug
https://savannah.gnu.org/bugs/index.php?33576 but launchpad wouldn't let
me
** Changed in: grub2 (Ubuntu Karmic)
Status: Incomplete =>
Submitted upstream as https://savannah.gnu.org/bugs/index.php?33576
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/428570
Title:
Default grub2 configuration won't boot through to default OS
To manag
> [...] I'm wondering if you had read this:
> http://ubuntuforums.org/showthread.php?t=1312798&highlight=grub
>From that thread (#7):
> After a forced shutdown (power loss) Grub waits at the menu ignoring the
> timeout options, some sort of
> "do you want recovery or normal boot?"
My headless
I have Lucid Lynx, and I'm getting this problem (grub2 menu showing up
and waiting forever), but the workaround in the initial comment
(GRUB_HIDDEN_TIMEOUT=1) doesn't work for me. This is grub-pc
1.98-1ubuntu9.
What I did find worked for me was to edit /boot/grub/grubenv, add
'recordfail=0', and
I don't need grub2. Do the masses?
I removed grub-pc and installed grub. I had to run update-grub to create
a menu.1st and grub-install /dev/sda to update the bootloader.
You my want to edit /boot/grub/menu.1st to taste.
I don't think a beta bootloader should be a default install for Karmic.
--
I tried another computer without known bios issues and also
1.97-beta4-1ubuntu5. with the default configuration.
I can reproduce the timer to not count down by going into recovery mode,
drop to a root shell, type reboot.
Next, the countdown does not kick in and the machine waits for a key.
--
D
Yes, Patrick, that is exactly what I am saying. After the initial
install of the OS, grub2 works. Should I have the temerity to actually
edit the configuration, like say... editing /etc/default/grub, it stops
working.
--
Default grub2 configuration won't boot through to default OS
https://bugs.l
I am also affected by this. It happens on my site on 2 different k7 desktop
machines.
those machines have issues with booting modern boot cd's like windows7beta. The
code 5 error comes up at least with one of them. So it might be an issue with
the older bios boot code.
I'm unsure how to reprod
Are you saying the workaround I posted to this bug doesn't work for you?
bpollen wrote:
> Only workaround I have found is to reinstall grub-pc and grub-common...
> EACH AND EVERY time you boot to Karmic. The it will time out and boot to
> the default OS. But the next time you boot to Karmic (wheth
Only workaround I have found is to reinstall grub-pc and grub-common...
EACH AND EVERY time you boot to Karmic. The it will time out and boot to
the default OS. But the next time you boot to Karmic (whether default or
not) you have to reinstall. If you don't, there is no countdown. At
least that
Im having the same issue described on
http://ubuntuforums.org/showthread.php?t=1312798&highlight=grub does
anybody know of a workaround?
--
Default grub2 configuration won't boot through to default OS
https://bugs.launchpad.net/bugs/428570
You received this bug notification because you are a memb
Jason Heblack wrote:
> Hi:
> I had an issue with karmic so now am on LTS 8.04. The issue was with
> grub2
> and I'm wondering if you had read this:
>
> http://ubuntuforums.org/showthread.php?t=1312798&highlight=grub
>
This does sound like it could be the same (or simi
Hi:
I had an issue with karmic so now am on LTS 8.04. The issue was with
grub2
and I'm wondering if you had read this:
http://ubuntuforums.org/showthread.php?t=1312798&highlight=grub
--
Default grub2 configuration won't boot through to default OS
https://bugs.launchpa
It looks like I'm still having this issue with beta 4 in the karmic
final, although it may or may not have degraded further: the
abovementioned workaround involving a non-zero value for
GRUB_HIDDEN_TIMEOUT does not appear to work, and GRUB boots to a menu on
every occasion; the only case where it d
> It's an unversioned dependency, so the old version satisfies the
> dependency just as well and therefore apt doesn't bother to upgrade it.
> (This may be an error in how the dependency is declared, but it's how it
> is right now.)
Can we call this a bug? It seems pointless to have a dummy packa
On Thu, Oct 08, 2009 at 02:32:00AM -, Patrick Goetz wrote:
> Yes, I understand, that's the point. If grub2 depends on grub-pc,
> shouldn't this have updated as well when I updated grub2?
It's an unversioned dependency, so the old version satisfies the
dependency just as well and therefore apt
Yes, I understand, that's the point. If grub2 depends on grub-pc,
shouldn't this have updated as well when I updated grub2?
I noticed the grub problem on the initial install of alpha4 (or the
current daily build, I can't remember which) and worked around it as
outlined in the bug report. When alp
The grub2 package itself contains nothing of any note. grub-common and
grub-pc are the packages it depends on that actually do something, and
you'd need to upgrade those. If you saw any effect from upgrading grub2
on its own, it was coincidental.
Package: grub2
Depends: grub-pc
Description: GRand
Steve Beattie wrote:
> Patrick: can you update to the current version of grub2 in karmic and do
> grub-install on your boot device (likely /dev/sda, but possibly not). I
> am unable to reproduce the behavior you see with the current version of
> grub2,
The current version is 1.97~beta3-1ubuntu8.
apt-get install grub2 updated the grub2 package to 1.97~beta3-1ubuntu8.
This appears to have fixed the problem, i.e. I ran
grub-install /dev/sda
and then changed the value of GRUB_HIDDEN_TIMEOUT back to 0 (the package
default)
GRUB_HIDDEN_TIMEOUT=0
ran grub-update, and the machine still boots
Patrick: can you update to the current version of grub2 in karmic and do
grub-install on your boot device (likely /dev/sda, but possibly not). I
am unable to reproduce the behavior you see with the current version of
grub2, but I did see it with an earlier install, and updating and
installing the n
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
** Also affects: grub2 (Ubuntu Karmic)
Importance: Medium
Assignee: Colin Wats
28 matches
Mail list logo
