URL:
  <https://savannah.gnu.org/bugs/?65854>

                 Summary: The default configuration for themes an fonts
overrides user modifications
                   Group: GNU GRUB
               Submitter: antymat
               Submitted: Sun 09 Jun 2024 09:32:23 AM CEST
                Category: Configuration
                Severity: Major
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: other
                 Release: 
         Discussion Lock: Any
         Reproducibility: Every Time
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Sun 09 Jun 2024 09:32:23 AM CEST By: Marcin Wolcendorf <antymat>
Block device configuration:

I have a fully encrypted system (except the EFI partition) with a separate
/boot (LUKS1 encrypted) partition and a LUKS2 encrypted PV for the LVM group.
All the themes, fonts (and encryption keys for the PV) are stored on the /boot
partition. There is no need to decrypt the PV in grub stage of boot, the
initramfs will have all the information to do it. 

The issue:

The grub configuration will make grub to, correctly, ask me first for the
password to the /boot, and then, immediately after and erroneously, for the
password to the PV. 

The "investigation":

In the 00_header, the initial part of the /boot/grub/grub.cfg is created. This
includes the fonts and the themes and their locations. The 00_header trawls
the configuration in /etc/default/grub for the location of the theme. Then
takes the name of the theme, disregards the given location and searches for
the theme in "known" locations and uses the first found:
/usr/share/desktop-base/grub-themes/. This results with the / being used, and
therefore makes it necessary to decrypt the PV it resides on. 

The proposal for fix:
Changing the order in which the "known" locations are searched for the theme
fixes the issue. For an example see the attached file. 










    _______________________________________________________
File Attachments:


-------------------------------------------------------
Name: theme_config_override.patch  Size: 658B
<https://file.savannah.gnu.org/file/theme_config_override.patch?file_id=56147>

    AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-e21a9f0b308156a6d1b2f4c9f7a463f076b621b8.tar.gz

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65854>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/


Reply via email to