Description of problem: I have today made two clean installations of Mga8 with my regular desktop machine onto an external hard drive. In both cases the plymouth background appears to be stretched vertically such that the "Mageia" logo characters are tall and thin. In my 'production' main Mga8 system which has been updated for the life of Cauldron this does not happen. In the new installs the grub2 and desktop backgrounds are correct and match my 1280x1024 monitor, as expected default.png points to the correct image: ├── default.jpg -> default.png ├── default.png -> /usr/share/mga/backgrounds/Mageia-Default-1280x1024.png ├── Mageia-Default-1024x600.png ├── Mageia-Default-1280x1024.png ├── Mageia-Default-1280x768.png ------snip------ The symlink in the plymouth theme also points correctly to default.png: themes ├── details │ └── details.plymouth ├── Mageia-Default │ ├── background.png -> ../../../../../usr/share/mga/backgrounds/default.png I suspect that plymouth is somehow using the 1280x768.png and resizing it to fit the screen but I cannot figure out why, when the link is correct. I will try to add a screen shot. Version-Release number of selected component (if applicable): plymouth-0.9.5-5.mga8 How reproducible: Clean Mga8 Net-install and re-boot. Twice, once with plasma once with LXDE. Steps to Reproduce: 1. 2. 3.
Created attachment 12326 [details] Rather poor screen shot
Thanks reporting this. Note that mga-bg-res, the script that is responsible to set the correct aspect ratio of our wallpaper has been switched to use 16:9 ratio instead of 4:3. But, it should handle 4:3 aspect ratio and set this properly but it seems it miss your monitor EDID and can't do it. So, as long as the script behave correctly to switch to default 16:9 aspect ratio, there is a no fix to do. Even some handle on this? Assigning to Donald who did the switch.
Assignee: bugsquad => watersnowrockSummary: Mga8 plymouth background stretched vertically in clean installs. => Mga8 plymouth background stretched vertically in clean installs with 4:3 monitorsStatus comment: (none) => 4:3 Aspect ratio not handled by plymouth? mga-bg-res does not switch?Target Milestone: --- => Mageia 8CC: (none) => ouaurelienSource RPM: plymouth-0.9.5-5.mga8.src.rpm => mageia-theme-8.0-2.mga8.src.rpm
Summary: Mga8 plymouth background stretched vertically in clean installs with 4:3 monitors => Mga8 plymouth background stretched vertically in clean installs with some 4:3 monitors
Found it! The *default* aspect ratio is used in the freshly installed initrd. It gets fixed later by rebuilding the initrd which happens automatically during kernel updates. I had never encountered this before even though I was involved in the original logic behind it, because until the default was changed recently from 4:3 to 16:9, my monitors *were* always at the default aspect ratio. So closing as expected behaviour :)
I switched the default to 16:9 from 4:3, fairly sure that this is what Plymouth will default to at install time. Does this happen during shutdown or just on reboot? If so, can you check if it persists after running dracut to rebuild your init? Noticed something similar when doing the new theme, there might be some triggers missing on the theme package to call for the rebuild on install.
(In reply to Barry Jackson from comment #3) > Found it! > > The *default* aspect ratio is used in the freshly installed initrd. > > It gets fixed later by rebuilding the initrd which happens automatically > during kernel updates. > > I had never encountered this before even though I was involved in the > original logic behind it, because until the default was changed recently > from 4:3 to 16:9, my monitors *were* always at the default aspect ratio. > > So closing as expected behaviour :) Will try and chase this down, I'm sure that Plymouth used to rebuild initrd on install/update, that should be added unless there was a compelling reason for it to not do so.
the post scripts have not changed since mga7, so if it worked there.. please attach /root/drakx/ddebug.log there might be a package ordering issue
Thinking the ordering through here, I assume that the mga-bg-res is only run at startup, after install, the link to default.jpg would be created after the initrd is built during install no matter what order things happen in. Solving this would require the initrd to be regenerated after the first boot or running mga-bg-res to get the monitor edid during install before initrd is built. Can a systemd service be run by the installer?
Created attachment 12330 [details] ddebug.log (tar.gz) Hi Thomas - ddebug.log attached. This net-install was done using all-nonfree.rdz and vmlinuz from current 8/cauldron repo to an external spinning USB hard drive. Barry
(In reply to Thomas Backlund from comment #6) > the post scripts have not changed since mga7, so if it worked there.. I'm not convinced it did. I would not have noticed as my monitor is the same as the old default. Only now that Donald changed it do I see the distorted graphic until dracut is run.
These comments are from mga-bg-res # Search for the optimal background resolution according to monitor-edid # Skip this during a local install (drakx-in-chroot or draklive2), as # monitor-edid sometimes hangs when run in a nested X session.
(In reply to Barry Jackson from comment #9) > (In reply to Thomas Backlund from comment #6) > > the post scripts have not changed since mga7, so if it worked there.. > > I'm not convinced it did. > I would not have noticed as my monitor is the same as the old default. Only > now that Donald changed it do I see the distorted graphic until dracut is > run. Yep - this behaviour was the opposite for me with a 16:9 screen, distorted first boot on mga7, fine now. See my above comment, I was wrong with thinking about the Plymouth scripts changing, they don't affect this.
(In reply to Barry Jackson from comment #10) > These comments are from mga-bg-res > > # Search for the optimal background resolution according to monitor-edid > # Skip this during a local install (drakx-in-chroot or draklive2), as > # monitor-edid sometimes hangs when run in a nested X session. Then it seems that the only fix for this re-running the initrd generation after the first boot has set the correct default.jpg/png links. Assuming that we want to keep the logo on the background, if we remove it, then this becomes a non issue, there will just be a distortion of the graphics which will be less noticeable. Or use a black screen with some boot animation like Fedora.
To be honest I really don't think it is worth worrying about. You made the right decision by changing the default to suit the majority of users, Most people won't notice and when the first kernel update comes along it gets fixed anyway. I think the colour of the bubbles in plymouth and the text in the installer side panel are more urgent to fix from a user's impression point of view :) I wish I had seen the background graphic choice sooner or I would have complained about the colour and brightness more loudly, simply because of all the text contrast issues it would cause. Anyway I prefer the logo to be there if we are voting :) Barry.