Cloning this bug for f34 because the f32 one is being closed. If this is inappropriate, sorry, but I don't have permission to modify the original bug to change the version and this issue is occurring for me on f34. +++ This bug was initially created as a clone of Bug #1739762 +++ Description of problem: When I boot the system via EFI, for one second grub shows an error about an missing file. Version-Release number of selected component (if applicable): grub2-efi-x64-2.02-62.fc29.x86_64 How reproducible: Every time Steps to Reproduce: 1. Boot the system Actual results: An error about the missing file unicode.pf2 is shown. Expected results: That no error is shown. Additional info: The missing file will be resend in many grub2 packages. --- Additional comment from Ben Cotton on 2019-10-31 18:57:57 UTC --- This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. --- Additional comment from Frank Büttner on 2019-11-01 16:17:30 UTC --- Same on F30 --- Additional comment from Loïc Yhuel on 2020-01-01 06:14:46 UTC --- Still present on F31, this prevents GRUB_GFXMODE from working. A manual workaround is to copy /usr/share/grub/unicode.pf2 to /boot/efi/EFI/fedora/fonts/unicode.pf2. /boot/efi/EFI/fedora/fonts/unicode.pf2 exists, but in grub2-efi-$arch-cdboot packages. I think it must be added to grub2-efi-$arch packages too. --- Additional comment from Ben Cotton on 2020-04-30 20:36:18 UTC --- This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. --- Additional comment from Frank Büttner on 2020-05-01 06:44:53 UTC --- Same on F31 --- Additional comment from Ben Cotton on 2020-11-03 15:32:11 UTC --- This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. --- Additional comment from Frank Büttner on 2020-11-03 16:49:56 UTC --- Also on F32 --- Additional comment from Andy Wang on 2021-04-23 05:03:59 UTC --- This is also occurring on F34. if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod btrfs search --no-floppy --fs-uuid --set=root 0568db24-ae30-4dfc-919c-ea994c777714 font="/root/usr/share/grub/unicode.pf2" fi It looks like it's trying to be smart enough to use btrfs to load the fonts from the btrfs root volume. I'm using btrfs encryption though. How would this work in that case? --- Additional comment from Frank Büttner on 2021-04-23 06:19:44 UTC --- It is file system independent, because I use XFS. --- Additional comment from Andy Wang on 2021-04-23 15:24:16 UTC --- (In reply to Frank Büttner from comment #9) > It is file system independent, because I use XFS. Are you using disk encryption? I was thinking that it's less related to the filesystem and more to that. But if you aren't then I dunno :) Just guessing. --- Additional comment from Frank Büttner on 2021-04-23 16:04:46 UTC --- Yes I use LUKS. Only the boot partitions is unencrypted. Here my disc layout: 1. EFI Boot FAT 2. Linux Boot XFS 3. Luks 3.1 LVM inside the luks container The rest(/, /home, swap, etc.) are an part of the lvm. --- Additional comment from Andy Wang on 2021-04-25 01:28:13 UTC --- I just reproduced this. Two identically installed fedora 34 VMs with one difference, I enabled disk encryption one, and did not on the other. Default installation options (btrfs, didn't make any changes). After installing added GRUB_TERMINAL=gfxterm to /etc/default/grub and grub2-mkconfig -o /boot/grub2/grub.cfg After rebooting, the same messages occur on the encrypted system and not on the unencrypted system. The grub.cfg has a similar block as I mentioned in comment #8. I think the issue is, that this is simply not able to read the font off the encrypted root filesystem. --- Additional comment from Fedora Program Management on 2021-04-29 15:56:14 UTC --- This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.