[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
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 this bug, which I solved somehow. -- 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 found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
@Teo, I had submitted comment #169, and I am sorry not to be of help when you were following those steps --I was in bed, being in a different time zone! In any case, I am happy that you could decipher the steps from my somewhat vague comment and succeeded in setting right grub. You have nicely summmarized the steps needed, and I agree with your conjecture. I hope this will be taken note of to resolve 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 found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
@jojive In my case, pressing F12 gave me the device booting order menu. It showed only my hard disk as the device (I have only one hard disk). However, below that it listed OS options: ubuntu twice (perhaps including earlier version) and also windows. Once could use arrow keys to select the OS to boot. However, using + and - keys one could change the order of the OS options in the menu. I checked this again today, since I did not remember clearly what I did the first time. @psusi I entirely agree with Teo in that the only way to make 13.04 work for me was to use boot repair. If that was a misconfiguration, why is that I could upgrade to 13.10 without a hiccup? If the upgrade to 13.10 worked without a problem, the upgrade to 14.04 is clearly following a different system which does not take care of what the upgrade from 13.04 to 13.10 could take care of. I also agree with Teo that those who are meant to fix the bug are not the ones who are helping, but people like us who are venting their frustrations also end up helping each other. -- 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 found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
I managed to solve the problem after a lot of struggle. I would like to summarize my efforts with my own idea as to how the problem was solved. (I will of course admit that I am not too knowledgeable!) Firstly, I discovered that the system was running EFI (so reconfiguring grub-pc did not work -- it is possible that I checked the wrong partition while doing this, but I am not sure if that did some harm). From the grub rescue stage, I found that I could go to grub stage using the following commands (sometimes only after using the full path and file name instead of /vmlinuz and /initrd.img) insmod linux linux /vmlinuz ro root=/dev/mapper/vg-root initrd /initrd.img The second of these commands gave error: premature end of file The last command gave unaligned pointer ox3880621b1a006275 Aborted. Press any key to exit. When I pressed a key, it gave me the grub menu, with all options of Ubuntu and Windows (until I ran boot-repair). So that was a partial success, despite the error messages. I booted into the latest Ubuntu version, and ran boot-repair with the recommended option. This did not help. http://paste.ubuntu.com/7403468 said An error occurred during the repair. The bottom line seemed to be : The boot files of [The OS now in use - Ubuntu 14.04 LTS] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a /boot partition (EXT4, 200MB, start of the disk). Since Windows 8 came pre-installed in the first partition, and since everything worked fine until upgrade to 14.04, I did not want to follow this suggestion, which would mean reinstalling everything. At this stage, I consulted a colleague in our computing centre. He found that in the bios boot priority list, windows came before ubuntu, and changed it to boot ubuntu first. After this change, the main problem was solved, and the system gave the grub menu with all operating systems listed. However, this worked fine for booting ubuntu, but on trying to boot windows it failed. At this stage, I remembered the posting of Fred Palmer on May 3 in this forum. He said that Boot-Repair does the rename for 'buggy' UEFI. He also said: To undo to rename files to their original names, you just need to tick the Restore EFI backups option of Boot-Repair. (See also the posting of SatPhil on May 2 in this forum, which is probably related). I followed this instruction and ran boot-repair with the option he mentioned. Now I have a system which boots correctly ubuntu as well as windows. I hope this will be helpful -- 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 found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
@Phillip, Windows was certainly loaded first (if I remember right, Windows 8 came pre-loaded on this touch-screen Lenovo Ideacentre all-in- one desktop). I did not use grub-cusomizer. However, what I do know is that when first attempts at loading Ubuntu 12.4 LTS and Fedora failed because they did not support the hardware on my machine, I installed Ubuntu 13.4 in July 2013. At that time, while I got the grub boot menu with Windows and LInux both listed, I could not boot any of them -- the system was just frozen. If I remember right, I booted using the live-CD and ran boot-repair, and that point onwards, everything worked fine. I then upgraded to 13.10 without any problem. There is a directory: /var/log/boot-sav/log/2013-07-22__11h25boot-repair43 which contains files boot-repair.log RESULTS.txt sda1 sda3 sda6 sda8 boot-repair.logb sda sda2 sda5 sda7 (of course, sd* are directories). If it helps, I can list one or more of these files. That of course is history. But I hope it helps to know how to repair what is broken. Thanks for your efforts. -- 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 found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
I upgraded from 13.04 (via 13.10) to 14.04, and found this problem, and I need help to straighten it. I get the grub rescue prompt with the error symbol `grub-term- highlight-color' not found. I managed to get the boot options after loading the kernel from the grub rescue prompt (though it did show some errors), and could boot into linux. After that, I am unable to reboot correctly, except by a series of commands at the grub rescue prompt. I found that I did not have the package grub-pc. I installed it however, and tried dpkg-reconfigure grub-pc. However, that has not helped. I tried to install boot-repair, but I get the following message: sudo add-apt-repository ppa:yannubuntu/boot-repair Cannot add PPA: 'ppa:yannubuntu/boot-repair'. Please check that the PPA name or format is correct. What I found, however, was that I have efi boot on the Windows partition. I need help to set things right, so that I can reboot without problem. Here are the outputs of blkid, df and debconf-show : sudo blkid /dev/sda1: LABEL=WINRE_DRV UUID=A8066BD9066BA6D2 TYPE=ntfs /dev/sda2: LABEL=SYSTEM_DRV UUID=546D-3E71 TYPE=vfat /dev/sda3: LABEL=LRS_ESP UUID=546E-285B TYPE=vfat /dev/sda5: LABEL=Windows8_OS UUID=B8146FC1146F816C TYPE=ntfs /dev/sda6: LABEL=Data UUID=401E71E21E71D180 TYPE=ntfs /dev/sda7: LABEL=PBR_DRV UUID=8A3269613269536D TYPE=ntfs /dev/sda8: UUID=b0766ae7-bc15-491d-b889-2c733ca06908 TYPE=ext4 /dev/sda9: UUID=b23dfdca-788a-4605-8a69-c1a25829f938 TYPE=swap df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda8 623487480 44357252 547435844 8% / none 40 4 0% /sys/fs/cgroup udev 4054856 12 4054844 1% /dev tmpfs 813120 1196811924 1% /run none51200 5120 0% /run/lock none 4065600 152 4065448 1% /run/shm none 102400 44102356 1% /run/user /dev/sda2 26214428564233580 11% /boot/efi sudo debconf-show grub-efi (no output) sudo debconf-show grub-pc grub-pc/disk_description: grub2/kfreebsd_cmdline_default: quiet splash grub-pc/mixed_legacy_and_grub2: true * grub2/linux_cmdline_default: quiet splash grub-pc/chainload_from_menu.lst: true grub2/device_map_regenerated: * grub-pc/install_devices: grub-pc/install_devices_failed: false * grub2/linux_cmdline: grub-pc/hidden_timeout: false * grub-pc/install_devices_empty: true grub-pc/kopt_extracted: false grub-pc/install_devices_disks_changed: grub-pc/partition_description: grub-pc/install_devices_failed_upgrade: true grub2/kfreebsd_cmdline: grub-pc/postrm_purge_boot_grub: false grub-pc/timeout: 10 Any suggestions for correcting the 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 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
@Phillip, sorry for my ignorance, grub-pc and grub-efi are new to me. I discovered that I use efi boot only after I installed grub-pc to try and follow suggestions from this forum. I remember having to use boot-repair when I installed 13.04 first, and that probably resulted in the present grub location. Yes, I do see grub as soon as I can boot. Also, I can do ls /boot/efi/EFI/Microsoft/Boot and get an output. -- 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 found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
@Phillip, sorry, here's the output of ls /boot/efi/EFI/Microsoft/Boot:
BCD boot.stl es-ES ko-KRqps-plocuk-UA
BCD.LOG bootx64.efi et-EE lt-LTResources zh-CN
BCD.LOG1 bootx64.efi.grb fi-FI lv-LVro-RO zh-HK
BCD.LOG2 cs-CZFonts memtest.efi ru-RU zh-TW
bg-BGda-DKfr-FR nb-NOsk-SK
bkpbootmgfw.efi de-DEhr-HR nl-NLsl-SI
bootmgfw.efi el-GRhu-HU pl-PLsr-Latn-CS
bootmgr.efi en-GBit-IT pt-BRsv-SE
BOOTSTAT.DAT en-USja-JP pt-PTtr-TR
and here is the output of sudo efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: ,0001,0003,0004,0005
Boot* Windows Boot Manager
HD(2,1f4800,82000,5e191502-eb3c-4c14-9cbf-d5fdcac1546a)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....
Boot0001* ubuntu
HD(2,1f4800,82000,5e191502-eb3c-4c14-9cbf-d5fdcac1546a)File(\EFI\ubuntu\grubx64.efi)
Boot0003* Windows Boot Manager
HD(3,276800,fa000,def6d7b2-4331-475f-9970-f39d10813f72)File(\EFI\Microsoft\Boot\bootmgfw.efi)
Boot0004* ubuntu
HD(2,1f4800,82000,5e191502-eb3c-4c14-9cbf-d5fdcac1546a)File(\EFI\Ubuntu\grubx64.efi)
Boot0005* ubuntu
HD(3,276800,fa000,def6d7b2-4331-475f-9970-f39d10813f72)File(\EFI\Ubuntu\grubx64.efi)
--
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 found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 943195] Re: xpdf.real crashed with SIGSEGV in GooHash::hash()
How do I install xpdf-3.03-11ubuntu3 on Ubuntu 13.4? If I do sudo apt-get install xpdf it tells me I have the latest version. Should this latest package not be a part of a normal update? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/943195 Title: xpdf.real crashed with SIGSEGV in GooHash::hash() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/943195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 149203] Re: If update-manager -d fails, you can't try again
Thanks for pursuing this issue. The point is that once I succeeded (by some means) in upgrading, there was no reason to go back and do the whole thing again. Nevertheless, it might be useful to someone if the details are recorded somewhere. Could you please give me a little time to check earlier exchanges of mails with someone (I do not think they were with you) and give you a summary. I cannot say anything from memory! Thanks. Saurabh _ On Thu, 8 Apr 2010, Rolf Leggewie wrote: Robin, Saurabh? Is this still an issue for you guys? Will close the ticket shortly if there are no further confirmations -- If update-manager -d fails, you can't try again https://bugs.launchpad.net/bugs/149203 You received this bug notification because you are a direct subscriber of the bug. -- If update-manager -d fails, you can't try again https://bugs.launchpad.net/bugs/149203 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149203] Re: If update-manager -d fails, you can't try again
As written earlier, I had a problem with upgrade from 7.04 to 7.10 using update-manager because of not enough free space. After that I could not get update-manager to give me the option to upgrade to 7.10. I have the following further information: I found that I could get update-manager (in feisty) to show the option to upgrade, after copying the correct meta-release file (obtained from changelogs.ubuntu.com) under .update-manager-core/ and /var/lib/update-manager/ (I had to be careful that the network proxy setting was correct -- setting network proxy for direct connection instead of the correct server ip address led to these files being replaced by html error messages). However, on clicking on the upgrade button, the upgrade fails, and update-manager hangs. If I had used update-manager -c from a terminal, the message is: Traceback (most recent call last): File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line 914, in on_button_dist_upgrade_clicked fetcher.run() File /usr/lib/python2.5/site-packages/UpdateManager/Core/DistUpgradeFetcherCore.py, line 153, in run if not self.showReleaseNotes(): File /usr/lib/python2.5/site-packages/UpdateManager/DistUpgradeFetcher.py, line 79, in showReleaseNotes release_notes = urllib2.urlopen(uri) File /usr/lib/python2.5/urllib2.py, line 121, in urlopen return _opener.open(url, data) File /usr/lib/python2.5/urllib2.py, line 366, in open protocol = req.get_type() File /usr/lib/python2.5/urllib2.py, line 241, in get_type raise ValueError, unknown url type: %s % self.__original ValueError: unknown url type: Traceback (most recent call last): File /usr/bin/update-manager, line 91, in module app.main(options) File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line 1017, in main gtk.main() KeyboardInterrupt -- If update-manager -d fails, you can't try again https://bugs.launchpad.net/bugs/149203 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149203] Re: If update-manager -d fails, you can't try again
I have the same problem. I had the same problem with the previous version of update-manager, and even after the very recent update of the update-manager to 1:0.59.26. -- If update-manager -d fails, you can't try again https://bugs.launchpad.net/bugs/149203 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 144370] Re: gv doesn't read ~/.gv at startup
I also had this problem with gv version 3.6.2 installed with feisty. After reading the above, I tried out the suggestion of making the changes in the file /etc/X11/app-defaults/GV, and it works. -- gv doesn't read ~/.gv at startup https://bugs.launchpad.net/bugs/144370 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
