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
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: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Teo1978, you are using an EFI booting machine, so don't have grub-pc
and the dpkg-reconfigure does not apply to you. IIRC, the problem on
EFI is that if you have used grub-repair or whatever it was called, it
makes a copy grubx64.efi and configures the firmware to boot that
instead of the
I want to try and run dpkg-reconfigure as suggested many times, so that
I can finally install grub updates and also upgrade the distribution,
without fear to brick my computer again due to this bug. Because it's
clear that if I'm going to wait for the bug to be fixed it's going to be
forever.
@cjwatson a year has passed since you said you had some idea about how
to fix this. Any progress on that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu 14.04 Update breaks
And finally it never asked me for the installation disk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu 14.04 Update breaks grub, resulting in error: symbol
Running
sudo dpkg-reconfigure grub-efi-amd64
this is the first question I get and I am already lost
│ The following Linux command line was extracted from /etc/default/grub or │
│ the `kopt' parameter in GRUB Legacy's menu.lst. Please verify that it is │
│ correct, and modify it if
Same Problem here
My workarounf was to enter the startup mode by pressing F12 (Dell Inspirion)
and boot from there. If not, I would see the error: symbol
'grub_term_highlight_color message from grub-rescue.
After a next update, instead of grub-rescue, I could only hear annoying beep
sounds,
Sorry, I forgot to mention: I am on an UEFI System.
---
sudo efibootmgr -v
BootCurrent: 0006
Timeout: 0 seconds
BootOrder: 0006,,2001
Boot* Ubuntu
HD(2,800,fa000,7f78ccae-b336-4d04-8c9f-ef1151bf4bb0)File(\EFI\ubuntu\grubx64.efi)RC
I've encountered the same problem. Is this an issue that won't be fixed?
I thought I had a pretty normal setup. Dual boot windows 7 and Ubuntu.
Installed Windows first, then Ubuntu, used all default/recommended settings.
Now left with a totally trashed bootloader for both OSes, and wasted best
Stanislav German-Evtushenko (giner): Actually, DO NOT DO #4, instead do
(as suggested above):
# dpkg-reconfigure grub-pc
Choose sda to match your list above (or others or all drives if you want
grub everywhere). This way it's safe(r) in case of future updates.
This will invoke the command
This is a bug and easily reproducible:
1. Install Ubuntu 10.04 server
2. Upgrade to 12.04 server (reboot is okay)
3. Upgrade to 14.04 server (reboot fails with grub error)
We've had this issue for all systems which was upgraded from 10.04. Here is a
work around which worked for us:
1. Install
dpkg-reconfigure asks you which drive or drives you want grub to be
installed to ( and reinstalled to during future upgrades ). If you only
have one drive then the choice is simple. If you have more than one,
then generally sda is the one your system boots from, but if you have
reconfigured your
So, I'm getting tired of always unchecking Grub from automatic updates
just to be sure that my system won't break again at the next reboot, and
I would also like to upgrade to Ubuntu 14.10, which I have been delaying
so far for the same reason (and then, 15.04 must be almost out). As a
remainder:
I just install Ubuntu 14.04.1 on a partition that previously had Ubuntu
13.10 on it. Now I can't access Windows or Ubuntu. All I get is the
grub_term_highlight_color missing message. What should I do now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/25/2014 4:21 AM, Zebulon wrote:
I just install Ubuntu 14.04.1 on a partition that previously had
Ubuntu 13.10 on it. Now I can't access Windows or Ubuntu. All I get
is the grub_term_highlight_color missing message. What should I do
now?
You
Sorry,the bug I've linked is about grub either breaking after an update
to 14.04 (for some people) or not working right after a clean install of
14.04 (for some other folks,including me):I somehow assumed that it
could be related to this one,although the error message is different.
--
You
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/1/2014 11:13 AM, cogset wrote:
Did you have a look at this other bug
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1311247 ?
You seem to have linked the wrong bug because that one doesn't say
anything at all like that.
-BEGIN PGP
I guess I did not make myself clear in #272. When the upgrade to 14.04
from 13.10 failed the first time, the message I got on attempted boot
was, error: symbol 'grub_term_highlight_color' not found. That
points to this bug. Bug 1311247 does not give that error.
--
You received this bug
Then your 14.10 install did not install grub correctly ( i.e. it
failed to install, or installed it to a place your system did not
actually boot from ), leaving the previous grub install you had to try
and fail to boot.
Which confirms there's a bug somewhere.
The bottom line is that this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/01/2014 06:20 AM, Teo wrote:
Which confirms there's a bug somewhere.
No, it does not. Installing grub to the wrong place because you
manually chose it is not a bug. Installing grub to /dev/sda by
default when your computer actually boots
No, it does not. Installing grub to the wrong place because you
manually chose it is not a bug.
Who talked about manually choosing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Never happen no matter what is asking for a magic wand and unicorns.
No matter what was a sloppy phrasing, agreed. I should have said whenever it
can be avoided. No need for magic wand or unicorns, just a few checks.
And here it definitlely can be avoided at least to some extend, while
On 11/01/2014 06:20 AM, Teo wrote:
Which confirms there's a bug somewhere.
No, it does not. Installing grub to the wrong place because you
manually chose it is not a bug. Installing grub to /dev/sda by
default when your computer actually boots from another drive is also
not a bug, because
Here is some information that might shed some light on the problem.
I am running Linux in a virtual machine (VM) using VirtualBox. I have a
working 13.10 VM that boots using /boot on /sda1, and a number of other disks
that are tied together using LVM. The /root, /home, etc. directories are all
@psusi,
You seem to not be listening to people.
All of the things that you say are the case are in fact not the case at
all. And all of the things that you say are not the case are precisely
the case.
I installed Ubuntu Gnome 14.10 by deleting all of my old Linux
partitions and installing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/31/2014 02:08 PM, Br. Peter Totleben, O.P. wrote:
All of the things that you say are the case are in fact not the
case at all. And all of the things that you say are not the case
are precisely the case.
Seeing as how there have been
That's not what I did, I installed Ubuntu via LiveCD and then did upgrade via
updater. I definitely didn't edit something manually.
I only used super grub disk to repair my grub after it was broken by the
updater. But go on close this bug. Let's pretend this never happens. Also it's
only grub,
This is ridiculous. Can someone else please fix the root cause? It's
well beyond obvious by now that Phillip Susi doesn't care at all about
ubuntu and its users.
It sounds like Peter Totleben has the most complete and useful
information so far - can you please submit a new bug report with your
If you fixed it correctly so the package system knows
where it needs to reinstall it in the future, then you won't
have the problem again. If you fixed it by manually reinstalling
grub outside the package system again, then you will face the problem again.
I'm not sure how I fixed it. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/30/2014 11:19 AM, Teo wrote:
Will I (and others in my situation) hit the problem again only
when dist-upgrading to 14.10 (which is already out btw) or also
when installing the grub updates that have been available for a
while? (which I have
Even though it might not be a bug in grub, it's a bug in Ubiquity (which
installs Grub the wrong way) or Ubuntu's updater (which updates Grub in
a wrong way). Most users have these problems because Grub was
automatically installed and upgraded, they had not configured it by
hand. So closing the
@psusi
No, as already discussed, there is a broken installation of grub. The reason
Colin reopened this report is because he wants to put in some checks at some
point to detect that it's broken and guide you through fixing it.
You start with No,, but you confirm what I said. Note I didn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/29/2014 4:37 AM, Mathias Dietrich wrote:
Even though it might not be a bug in grub, it's a bug in Ubiquity
(which installs Grub the wrong way) or Ubuntu's updater (which
updates Grub in a wrong way). Most users have these problems
because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/27/2014 11:52 PM, Br. Peter Totleben, O.P. wrote:
The problem here is actually a bug that is internal to grub itself,
and not to Ubuntu, per se. The problem is that Ubuntu Trusty
(14.04) and Ubuntu Utopic (14.10) both include buggy versions
@psusi how can you tell that? A lot of people may have broken something
in their grub that was exposed during the upgrade, but what about the
others that found the problem with a plain system and a fresh install?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/28/2014 01:07 PM, aldo wrote:
@psusi how can you tell that? A lot of people may have broken something
in their grub that was exposed during the upgrade, but what about the
others that found the problem with a plain system and a fresh
I haven't seen anyone report this on a fresh install. It is always
after an upgrade,
That's untrue and you know it.
There are a few comments on this very page reporting the issue on fresh
install. And you did see them; I seem to remember you said you just don't
believe them (I'm too lazy to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/28/2014 09:34 PM, Teo wrote:
Anyway, as already discussed, there is clearly some bug, whether it
is in Grub or in Ubuntu, if a perfectly working dual boot (whether
it was a fresh install or it was tinkered because that is the
_only_ way
I have only encountered this if [for example] I had grub originally
installed in some pbr (eg; sda6) and I later changed the location to the
mbr (eg; sda) using grub-install /dev/sda rather than using dpkg-
reconfigure grub-pc. Then apparently the release-upgrade reads the prior
dpkg info
My answer to Teo's question regarding upgrades:
I have had no problem with updates of any of 10.04 packages. My history
is that I did a fresh install of 9.04, ran into a problem which I could
solve using grub-repair, then upgraded to 9.10 without any problem, and
during upgrade to 10.04 ran into
Note that this problem also exists in Ubuntu 14.10.
Before I get in to all of this, I should explain my setup, so that
people who are interested in my solution can figure out if they are in a
similar boat. I have a Dell Inspiron laptop with UEFI and a Windows 8
partition. (Earlier I had already
Folks,
I was bit by this today, turning my dual-bootable laptop into a brick.
I tried a lot of things here and nothing worked.
What did work for me was following directions in
http://community.linuxmint.com/tutorial/view/245
I'm running Linux Mint 17 Qiana, which is based on Ubuntu 14.04
I was
@cjwatson again, could you please tell us whether or not it is safe to
install the latest grub updates for those of us who had the bug, had the
boot broken, and had fixed it?
The problem is: there are updates available and I have no idea whether
installing them will cause the same thing to run
I run the release upgrade from a completely up-to-date 12.04 from the Update
Manager and it completed without problem. After the upgrade had finished I
performed the restart and faced the
grub rescue
prompt and got puzzled understandably.
Then I searched and found this bug and figured out that
I can confirm that there is some regression going from grub2 2.00 to
2.02~beta2.
I have disk0 with traditional partition table and three partitions:
sda1 is Windows boot
sda2 is Windows system
sda3 is linux Mint root partition (with /boot inside it)
In the past I manually set up the Windows
I am still trying to fix my system after upgrading from xubuntu 13.10 to
14.04 (amd64). I ran boot-repair after installing 13.10 like many
others. No hardware change since I bought the system. I have a hybrid
harddisk, but the SSD is only used by Windows. BIOS config is UEFI with
secure boot
I've made a clean install on a 13.04 dual-boot, efi notebook. first boot
i got that error message. i tried boot-repair with and without secure-
boot (disabled by bios), but that didn't worked. Here is the url of the
report: http://paste.ubuntu.com/7951398/
so i tried to reset grub manually with
to be precise, here is my last boot-info report:
http://paste.ubuntu.com/8159797/.
strange thing is that on the last run in the log i found this:
locating grub_term_highlight_color at 0xb7e8 (0xb4e0).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Teo:
I updated grub, but afterwards, just to be sure, I ran the grub-install
command like I did when I repaired my non-booting system.
My laptop still boots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment removed: Screenshot from 2014-07-24 13:30:10.png
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+attachment/4161851/+files/Screenshot%20from%202014-07-24%2013%3A30%3A10.png
** Attachment removed: Screenshot from 2014-07-24 13:30:10.png
@Colin Watson: Thanks for taking the time to look into this. I was left
very disheartened earlier in the year when I upgraded, hit this problem
and then was just dismissed.
The reason I am commenting now is I ran an apt-get dist-upgrade
yesterday. I booted the machine this evening and have hit
@cjwatson do you know the answer to my question in comment #234?
I have stopped updating my system since the update for grup has become
available, because I fear I may incur in the same issue again. I think
everybody who has had this issue and recovered from it urgently needs to know
whether
I DID attach the file while writing the previous comment. I didn't forget to
attach it.
It simply didn't get through for some reason. Here it is again.
** Attachment added: Screenshot from 2014-07-24 13:30:10.png
Ok, now the time has come to be scared.
Given that upgrading from 13.10 to 14.04 broke my boot and bricked my
computer because of this bug, and that I fixed it (long ago) using the
methods that have been commented above, and I have a wonderfully working
14.04 (in dual boot with Windows 8),
WILL
Fuck it, what the hell is wrong with Launchpad? Why doesn't it accept
the attachment and doesn't even show an error message???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu
** Attachment added: Screenshot from 2014-07-24 13:30:10.png
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+attachment/4161856/+files/Screenshot%20from%202014-07-24%2013%3A30%3A10.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
F*** it, Launchpad silently discards the screenshot every time I try to
attach it to this report, and it even keeps showing a confirmation that
it has been attached though it doesn't show up anywhere.
However for some reason it has allowed me to attach it to another report, so
here's the link to
Comment #14 helped me. I have dualboot laptop with Windows on the first
disk where the old grub was installed and the second disk with Linux
partition.
The issue was that the grub on the second disk was upgraded, but on the
first one, that was actually used, wasn't.
I used USB installation disk
I can't believe that anyone may chalk this up to a supposedly incorrect
setup:as many others have reported,I've just done a clean install
(Lubuntu Trusty) from CD to a new hard drive,the installation process
finished normally and then the system could not be booted,period.
After fiddling with
I fix this by boot repair tool, very easy to use and worked for me (upgrade
13.10 to 14.04LTS).
refer: http://askubuntu.com/a/229982
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Thanks @palmar, easy fix, works well.
I did it with a lubuntu live-cd, but same all...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu 14.04 Update breaks grub, resulting in
This happened to me when upgrading from 13.10 to 14.04.
I did not have any special Grub settings as far as I know.
I was unable to manually boot from the Grub rescue prompt as it could
not read the partition filesystems (said they were msdos while they are
ext).
I tried the recommended solution
Update: the boot repair disk fails to boot, because of the PAE bug.
Adding forcepae to the boot options does not help either. However,
Super Grub2 Disk does boot, recognizes the config and can be used to
boot the system. Now I have the safest laptop ever! Nobody can boot it
but me!
In the
I got my machine too boot again:
* I Used the Super Grub Disk to boot into the existing installation on my laptop
* I checked /etc/mtab to see which device was mounted (in my case /dev/sda)
* then I ran sudo grub-install --boot-directory=/boot /dev/sda
For people using the Super Grub Disk:
I know a lot has been said already, but I want to add my case just for
the record. It just might contain info on what went unexpectedly right
or wrong when it shouldn't have.
I had a working 13.10 installation on a (pretty ancient but
indestructible) Panasonic CF-18 Toughbook. This is one of the
My experience with this problem:
1- Use Super Grub Disk to start.
2- cd /etc/grub.d
3- sudo su
4- cp -a 05_debian_theme 05_debian_theme_old
5- Delete all in the file 05_debian_theme until last line with nano o vim.
don't delete the last line -set_default_theme
6- sudo grub-install --recheck
@Colin Watson: any updates on the bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu 14.04 Update breaks grub, resulting in error: symbol
'grub_term_highlight_color' not
@ Colin Watson: Although I originally wanted to unsubscribe from this
bug, to avoid the daily comments from this bug, I have to admit that it
is good to hear that this is finally recognized as bug. As the original
reporter of this bug, I can provide all the necessary configuration
about my HDD
I too experienced this bug: my perfectly-functional Ubuntu 13.10
(x86_64) system was rendered unbootable on upgrade to 14.04 with the
grub grub_term_highlight_color error. My computer has two disk drives:
one with Windows 8 and one with Ubuntu. I use GPT/EFI exclusively, with
secure boot turned
I also encountered (bug description on top)
I found Boot-Repair advanced Settings Secure Boot to be enabled
while in BIOS Settings it was not. So i simply switched the Setting in
BIOS to enabled and error disapeared.
HP Pavilion g6 3277sz
Kind regards
Markus
--
You received this bug
I forgot to indicate (#221)
efi/gpt
Kind regards
markus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu 14.04 Update breaks grub, resulting in error: symbol
I copied a hard disk with kubuntu 13.10 to a new (bigger) one with dd,
taking extra care to verify the copy with hashing it using md5sum. The
copy was fine.
It bootet correctly, everything behaved normally.
After the upgrade to 14.04, the system didn't boot any more because of
the error
I see a lot of activity on this subject and as an end user I am going to
try 13.10 now since 14.04 failed to install on a clean machine. If I
have to go through all the extra trouble to install this version on a
clean machine then what is the point of installing it to begin with. It
has been years
@robert-tindall I think you are definitely on to something. Your
suggestions did help although my circumstances differed.
I was running 14.04 with a downgraded version of grub due to this issue.
I decided to go ahead and do a dist-upgrade. After that I would this
error msg that everyone has been
Phillip, please do not close this bug again. As the Debian/Ubuntu grub2
maintainer, I have a list of things that I intend to do here and I do
not need you telling users to go away before I have a chance to do so.
** Changed in: grub2 (Ubuntu)
Status: Won't Fix = Triaged
--
You received
On Tue, May 27, 2014 at 09:08:50AM +1000, Phil Diacono wrote:
There is a lot of dissatisfaction about a problem that causes updates to
Ubuntu 14.04 to fail to boot. Phillip Susi of Ubuntu feels this is not
a bug whereas everyone who runs into feels that it is. We suspect it
may affect many
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/29/2014 6:34 AM, Colin Watson wrote:
I have reopened this bug. Phillip, please could you refrain from
triaging grub2 bugs in this way? It creates *more* work for me,
not less, and does not help. It would in fact help me if there
were as
On Thu, May 29, 2014 at 09:40:34AM -0400, Phillip Susi wrote:
Indeed, part of the problem is that everyone piled into the same bug
with several different issues rather than troubleshooting it on a case
by case basis.
This certainly happens, and I realise that's annoying; any bug like this
is
At a bare minimum, can't you detect whether the user has multiple hard
drives and warn them before upgrading if they do and reference this bug
report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well. Add me. Single drive, single boot, fresh 13.10 install using LVM
and an encrypted partition. Upgraded to 14.04...and dead. So far
running dpkg-reconfigure has been pointless, as have all the other steps
I've tried. I find it rather amusing that the canned response is not a
bug, you've
Well, gosh. That was EASY! Here's the simple steps I used to fix this;
the sort of thing any generic user should be able to pull out of thin
air. The gist is I booted to an xubuntu 14.04 live CD, mounted and
chrooted to my normal system, then ran dpkg-reconfigure and update-grub.
I selected
@Phillip Susi
I think the bug occurred for me because i changed sda to another hdd
(where windows is), so the entries from debconf did not match the new
hdd and therefor grub did not install itself on sda, only on sdb
(linux), with the new version.
Don't you think this behavior is unwanted?
_dan_(dan-void).. That happens when grub is your boot loader manager. Even in
old versions with multiple operational systems the grub in it self was not the
problem. Usually when i install ubuntu and i thick the radio button to install
with what ever existing operation system is on the hda or
If it is the issue of recovering of bad ' grub 2 ' then you can do this
as in this video.
https://www.youtube.com/watch?v=ajs9rO5upZA
Getting your fingers used to fixing some simple admin tasks is part of
getting to understand how Ubuntu works. I understand that in the
beginning anything new can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/28/2014 10:53 AM, _dan_ wrote:
Don't you think this behavior is unwanted? Should a user have to
know to rerun dpkg-reconfigure grub-pc when he/she changes the
windows hdd, which has nothing to do with the Linux installation?
Should not take
IMHO, that bug simply shows that dist-upgrade breaks the boot by blindly
(re)installing GRUB whatever the boot setup is.
In other words, dist-upgrade does not support enough boot configurations.
A very simple and quick fix is: dist-upgrade should not install any
bootloader. (why taking the
If you feel this bug is real, please provide a series of steps that will
break GRUB consistently in any given system.
Then you're allowed to set the status back to confirmed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For me it was this:
1) Install ubuntu 13.04
2) Upgrade to 13.10
2) Attempt to upgrade to 14.04 = this bug, unusable system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu 14.04
When you are Migrateing - to 14.04 LTS from previous any linux or have
multiboot systems do this. When you are updateing a new KERNEL in your new
installation or after complete new installation. New KERNEL module will be
loaded up to make your 14.04 LTS have latest drives etc. After update or
http://www.omgubuntu.co.uk/2011/07/kernel-entries-gone
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu 14.04 Update breaks grub, resulting in error: symbol
Psusi: There is nothing we can do to prevent or detect this kind of
misconfiguration.
Are you basing this on just one commenter's output in comment #13 in
which case the configuration is in fact bad? Or have you seen more bad
configurations that led to this issue.
I'm just still not convinced
just a few thoughts (opinions ;) )...
I have posted previously in the thread and followed it since then. I
sympathise with both sides - both 'its a bug' and 'its the user' but on
consideration IMHO neither are 100% right.
My hardware is a Dell box with an Intel RAID controller set up with one
Adam, so far there have been two variations on the problem presented:
1) You are booting in bios mode with grub-pc, and grub-
pc/install_devices is not set, which results in the MBR not being
reinstalled on upgrade. There are systems on which this is a perfectly
valid configuration ( i.e. if
When the noise stops, the melody sounds.
So keep it easy peace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289977
Title:
Ubuntu 14.04 Update breaks grub, resulting in error: symbol
Phillip, You know what causes this problem, so you can test for it
before the upgrade starts. Wouldn't it be better to put an advisory
comment up, warning the user that the system has a legitimate but
possibly troublesome configuration? The comment could either fully
explain how the trouble
All this noise is complicating the issue. It's really simple - there's
a bug somewhere because as a user of Ubuntu 13.10 with no custom
configs, no second OSs, and no extra hard drives, I followed the
upgrade procedure that was presented to me and was left with an unusual
system.
I'm moving the
The bug is in your configuration. As a developer, I have said there is
nothing we can do on our end to mitigate this. As a user you need to
avoid using grub-repair to get into an unsupported configuration. At
this point your recourse is to take it up with the technical board.
** Changed in:
Phillip you keep missing three things that have been said several times
very clearly:
- there are users that NEVER used boot-repair (or grub-repair as you call it)
and experienced the issue anyway
- there are situations where you CANNOT avoid using it as it's the only way to
get Ubuntu to work
Update breaks grub, resulting in
error: symbol 'grub_term_highlight_color' not found
Date: Mon, 26 May 2014 20:56:47 -
From: Phillip Susi ps...@ubuntu.com
Reply-To: Bug 1289977 1289...@bugs.launchpad.net
To: satp...@gmail.com
The bug is in your configuration. As a developer, I have said
1 - 100 of 303 matches
Mail list logo
