Bug 1191728 - Theme & default boot section cannot be modified during installation
Theme & default boot section cannot be modified during installation
Status: CONFIRMED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: YaST Team
Jiri Srain
https://trello.com/c/cluBFJCC
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-10-18 05:30 UTC by Joaquín Rivera
Modified: 2021-10-20 08:04 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
logs in the installed system after chaning theme (5.63 MB, application/x-bzip)
2021-10-18 05:31 UTC, Joaquín Rivera
Details
folder with themes, extracted from latest tw installation (27.54 KB, application/x-bzip)
2021-10-18 05:33 UTC, Joaquín Rivera
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joaquín Rivera 2021-10-18 05:30:54 UTC
Step to reproduce:

(1) Get the exact theme that contains an installed system:
- Boot latest TW at the moment:
https://openqa.opensuse.org/tests/1974756/asset/hdd/opensuse-Tumbleweed-x86_64-20211016-gnome@64bit.qcow2
- Gain sudo, pass for that openQA qcow2, as always: nots3cr3t
- Navigate to the folder with the current theme:
/boot/grub2/themes/openSUSE/
- gimp logo.png for example, changing a bit the image
- Save all the files in that folder to local system.

(2) Apply that modified theme to new installation:
- Via console, transfer all files to new folder created in the installer with name '/themes/'.
- In the UI, in Boot Loader Settings in Kernel Parameters tab I fill Console Theme with /themes/theme.txt, click OK and click Install.

(3) Reaches text mode console instead of graphical console, probably because of some hidden failure (?)
Comment 1 Joaquín Rivera 2021-10-18 05:31:30 UTC
Created attachment 853184 [details]
logs in the installed system after chaning theme
Comment 2 Joaquín Rivera 2021-10-18 05:33:24 UTC
Created attachment 853185 [details]
folder with themes, extracted from latest tw installation

I also try to get the files from the package and same result.
Comment 3 Joaquín Rivera 2021-10-18 07:20:43 UTC
As requested offline, in /etc/default/grub is present the value:
GRUB_THEME=/themes/theme.txt

But that folder does not exist in the installed system.
Comment 4 Josef Reidinger 2021-10-18 08:29:37 UTC
(In reply to Joaquín Rivera from comment #3)
> As requested offline, in /etc/default/grub is present the value:
> GRUB_THEME=/themes/theme.txt
> 
> But that folder does not exist in the installed system.

And that is probably issue as we run grub in target system, so it cannot see insts-sys content. Idea is that if you have installed multiple themes, you can pick one, but not to modify it in insts-sys.
Comment 5 Joaquín Rivera 2021-10-18 08:55:26 UTC
So, that means that the feature doesn't make sense in installation, right? Should be the field hidden during installation?
Because the user doesn't install anything, during installation the content of the package is extracted and used as default.
Comment 6 Joaquín Rivera 2021-10-20 04:56:30 UTC
Similar thing happen with Default boot section during installation (not in the installed system)

I tried to find the use case, even having a different OS, for example TW + Leap, but that section is not filled, os-prober doesn't find anything.

I will suggest hide both fields, as I cannot find a way to use them during installation.