I built two virtual machines a couple of weeks ago from the 10.04.2
server iso and fully updated them. The most recent update of grub
(1.98-1ubuntu12) caused this problem again when they updated. I also saw
it on about 25% of my other VMs, so it is not isolated to new installs.
This bug needs to
does anyone even read these things?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/678316
Title:
Option 'No' at question 'Continue without installing GRUB?' does
nothing. Forced to answer 'Yes'.
This is happening again when upgrading to 1.98-1ubuntu8
--
Option 'No' at question 'Continue without installing GRUB?' does nothing.
Forced to answer 'Yes'.
https://bugs.launchpad.net/bugs/580408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: grub2
This is a dupe of Bug #580408, but I don't seem to be allowed to reopen
that one.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
Option 'No' at question 'Continue without installing GRUB?' does nothing.
Forced to
I get stuck in the same loop when doing the upgrade to 1.98-1ubuntu7.
System is a simple VM with 10.04 Server 64bit, all in one partition
--
Option 'No' at question 'Continue without installing GRUB?' does nothing.
Forced to answer 'Yes'.
https://bugs.launchpad.net/bugs/580408
You received this
I don't think it was ever a problem in later releases, just in the
hardy-updates repository. Read this:
https://answers.launchpad.net/ubuntu/+source/linux/+question/54061
It looks like the kernels are now being compiled with gcc 4.2.4, so it
seems fixed to me.
--
hardy-updates needs a new
I have an apt-cacher on both gutsy (1.5.3) and hardy (1.5.5). The patch
from the link above worked on both (same code, different line numbers--
it's pretty easy to find by the comment above it).
Would very much like to see this patched in Ubuntu rather than waiting
on an upstream patch that might
So is this a 3+ month old server misconfiguration that's preventing
anyone from upgrading from feisty? What's going on???
--
Failed Upgrade tool signature when using do-release-upgrade
https://bugs.launchpad.net/bugs/156070
You received this bug notification because you are a member of Ubuntu
