Description of problem: I installed F18 in UEFI mode, then upgraded to F19. Every time I boot the machine, I see the following error messages: > error: file `/grub2/themes/system/DejaVuSans-10.pf2' not found. > error: file `/grub2/themes/system/DejaVuSans-12.pf2' not found. > error: file `/grub2/themes/system/DejaVuSans-Bold-14.pf2' not found. > error: file `/grub2/themes/system/theme.txt' not found. > > Press any key to continue... The errors are not fatal, I can get to the grub menu, but they are displayed on every boot. Every time I click on any submenu in grub, I see one more error: > error: file `/grub2/themes/system/theme.txt' not found. > > Press any key to continue... Again, not fatal, I can continue working. Version-Release number of selected component (if applicable): grub2-efi-2.00-22.fc19.x86_64 How reproducible: tried one upgrade, happens on every boot Steps to Reproduce: 1. install default F18 in UEFI 2. upgrade to F19
Created attachment 765180 [details] error on boot
Created attachment 765181 [details] error on submenu
Created attachment 765182 [details] boot_contents
Created attachment 765183 [details] etc-default-grub
Created attachment 765184 [details] fedup.log
Created attachment 765185 [details] grub.cfg
When I ran "grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg", the problem disappeared. But that won't happen for general users, or will it?
Created attachment 765187 [details] grub.cfg after re-running grub2-mkconfig I noticed that in the new grub.cfg these lines are gone: > loadfont ($root)/grub2/themes/system/DejaVuSans-10.pf2 > loadfont ($root)/grub2/themes/system/DejaVuSans-12.pf2 > loadfont ($root)/grub2/themes/system/DejaVuSans-Bold-14.pf2 > set theme=($root)/grub2/themes/system/theme.txt > export theme Shouldn't fedup take care of re-generating grub? Or of it did, why the theme lines weren't already removed?
Same error, non-UEFI; F18 -> F19 upgrade. grub2-2.00-22.fc19.x86_64 grub2-tools-2.00-22.fc19.x86_64 grub2-efi-2.00-22.fc19.x86_64 grub-efi-0.97-93.fc17.x86_64 I've got EFI and non-EFI grub because of Samsung. Non-EFI boot at the moment.
I have reproduced the same with i386 upgrade. It seems to affect all architectures.
CCing Will Woods. Will, is this something that should be fixed inside fedup, or inside grub?
The answer is always "package problems belong to the packagers". I can't be an expert on the config files for every package in Fedora. If the snmpd config needed to be updated, you'd ask the net-snmp maintainers. If the PAM config needed to be updated, you'd ask the pam maintainers. So if the GRUB config needs to be updated, you ask the grub maintainers. With that said: if I had to guess, I'd say this is probably another manifestation of whatever's happening in bug 975800.
Probably not fedup. I went F18 -> F19 a while ago. It has been running fine for weeks (different Grub theme errors at different times, though, eg. bug 964375). Grub was fine last week. I have used PackageKit/yum to upgrade packages. So, from /var/log/yum.log: Jun 18 11:09:34 Updated: 1:grub2-tools-2.00-20.fc19.x86_64 Jun 18 11:10:40 Updated: 1:grub2-2.00-20.fc19.x86_64 Jun 18 11:10:42 Updated: 1:grub2-efi-2.00-20.fc19.x86_64 Jun 24 10:02:16 Updated: fedora-logos-19.0.4-2.fc19.noarch Jun 24 10:02:18 Updated: 1:grub2-tools-2.00-22.fc19.x86_64 Jun 24 10:02:40 Updated: 1:grub2-efi-2.00-22.fc19.x86_64 Jun 24 10:02:41 Updated: 1:grub2-2.00-22.fc19.x86_64 I think June 24 broke it for me.
*** This bug has been marked as a duplicate of bug 975800 ***