Bug 977962

Summary: files not found after upgrade from F18 to F19
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: grub2Assignee: Peter Jones <pjones>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bcl, berend.de.schouwer, dennis, mads, pjones, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-02 08:28:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
error on boot
none
error on submenu
none
boot_contents
none
etc-default-grub
none
fedup.log
none
grub.cfg
none
grub.cfg after re-running grub2-mkconfig none

Description Kamil Páral 2013-06-25 16:54:31 UTC
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

Comment 1 Kamil Páral 2013-06-25 16:54:57 UTC
Created attachment 765180 [details]
error on boot

Comment 2 Kamil Páral 2013-06-25 16:55:18 UTC
Created attachment 765181 [details]
error on submenu

Comment 3 Kamil Páral 2013-06-25 16:58:21 UTC
Created attachment 765182 [details]
boot_contents

Comment 4 Kamil Páral 2013-06-25 16:58:26 UTC
Created attachment 765183 [details]
etc-default-grub

Comment 5 Kamil Páral 2013-06-25 16:58:33 UTC
Created attachment 765184 [details]
fedup.log

Comment 6 Kamil Páral 2013-06-25 16:58:55 UTC
Created attachment 765185 [details]
grub.cfg

Comment 7 Kamil Páral 2013-06-25 17:00:43 UTC
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?

Comment 8 Kamil Páral 2013-06-25 17:04:48 UTC
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?

Comment 9 Berend De Schouwer 2013-06-26 14:10:06 UTC
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.

Comment 10 Kamil Páral 2013-06-26 14:26:19 UTC
I have reproduced the same with i386 upgrade. It seems to affect all architectures.

Comment 11 Kamil Páral 2013-06-26 14:27:44 UTC
CCing Will Woods. Will, is this something that should be fixed inside fedup, or inside grub?

Comment 12 Will Woods 2013-06-26 19:10:17 UTC
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.

Comment 13 Berend De Schouwer 2013-06-27 08:15:55 UTC
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.

Comment 14 Kamil Páral 2013-07-02 08:28:41 UTC

*** This bug has been marked as a duplicate of bug 975800 ***