search

OpenMandrivaAssociation / distribution

OpenMandriva Lx is an exciting free Desktop Operating System that aims to cater to and interest first time and advanced users alike. It has the breadth and depth of an advanced system but is designed to be simple and straightforward in use.
https://openmandriva.org
7 stars 2 forks source link

OpenMandriva splash theme (Plymouth?) no longer appears at bootup in VirtualBox #2841

Closed edwardp3 closed 1 year ago

edwardp3 commented 1 year ago

OpenMandriva version: Cooker (possibly Rolling, once kernel is updated)

Describe the bug: System updated, including a new kernel. Upon boot up, the OpenMandriva splash screen no longer appears, all that appears now is a black screen with three white small blocks. Both in Plasma and Xfce, not desktop-dependent.

Steps to reproduce: Updated kernel to 5.19.8

Observed behavior: OpenMandriva splash screen no longer appears.

Expected behavior: Splash screen should have appeared as it did with the 5.19.7 kernel.

Additional comment: Some years back, had the exact same issue occur with Fedora installed on HDD (no VirtualBox), it was determined to be kernel-related pertaining to the video at the time. Occurs in VirtualBox using VMSVGA (VMware) and VBoxSVGA (VirtualBox). Unable to locate original Fedora bug report on their system.

Logs and screenshots if relevant

Screenshot taken with mobile.

splash

omakuta commented 1 year ago

This issue has been mentioned on OMA forum. There might be relevant details there:

https://forum.openmandriva.org/t/5-19-8-kernel-upodate-in-cooker-virtualbox-no-longer-causes-plymouth-splash-screen-to-display/4646/1

rugyada commented 1 year ago

Expected behavior: Splash screen should have appeared as it did with the 5.19.7 kernel.

Confirming the plymouth bug however it happens also with 5.19.7-desktop https://forum.openmandriva.org/t/5-19-8-kernel-update-in-cooker-virtualbox-no-longer-causes-plymouth-splash-screen-to-display/4646/2

hence I cannot confirm the supposed reason.

tpgxyz commented 1 year ago

Yes i can confirm this issue on real hardware on aarch64.

I regenerated initrd (dracut -f) for older kernel-5.19.5 and i get wrong plymouth splas too, so this is not a kernel issue.

edwardp3 commented 1 year ago

kernel-desktop-gcc 5.19.8 also did not cause the OM splash screen to display. History from dnf is also below.

I do not know if this is relevant, but when I just removed kernel-desktop-gcc, there was a reference to fgrep being obsoleted, replaced with grep -F: 

Running transaction
  Preparing        :                                                        1/1 
  Erasing          : kernel-desktop-gcc-5.19.8-1.x86_64                     1/1 
  Running scriptlet: kernel-desktop-gcc-5.19.8-1.x86_64                     1/1 
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/background.png
Found linux image: /boot/vmlinuz-5.19.8-desktop-1omv4090
Found initrd image: /boot/initrd-5.19.8-desktop-1omv4090.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-5.19.7-desktop-1omv4090
Found initrd image: /boot/initrd-5.19.7-desktop-1omv4090.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found linux image: /boot/vmlinuz-5.19.6-desktop-1omv4090
Found initrd image: /boot/initrd-5.19.6-desktop-1omv4090.img
fgrep: warning: fgrep is obsolescent; using grep -F
Found memtest image: /boot/memtest.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
done
  Verifying        : kernel-desktop-gcc-5.19.8-1.x86_64                     1/1 

Removed:
  kernel-desktop-gcc-5.19.8-1.x86_64                                            

Complete!

dnf transaction history:

Command Line   : dsync
Comment        : 
Packages Altered:
    Install       kernel-desktop-5.19.8-1.x86_64            @cooker-x86_64
    Install       pavucontrol-qt-1.1.0-2.x86_64             @cooker-x86_64
    Upgrade       cpupower-6.0.0-0.rc4.2.x86_64             @cooker-x86_64
    Upgraded      cpupower-6.0.0-0.rc4.1.x86_64             @@System
    Upgrade       dnf-4.14.0-1.noarch                       @cooker-x86_64
    Upgraded      dnf-4.13.0-3.noarch                       @@System
    Upgrade       dnf-data-4.14.0-1.noarch                  @cooker-x86_64
    Upgraded      dnf-data-4.13.0-3.noarch                  @@System
    Upgrade       lib64bpf1-6.0.0-0.rc4.2.x86_64            @cooker-x86_64
    Upgraded      lib64bpf1-6.0.0-0.rc4.1.x86_64            @@System
    Upgrade       lib64pulseaudio-16.1-4.x86_64             @cooker-x86_64
    Upgraded      lib64pulseaudio-16.1-3.x86_64             @@System
    Upgrade       lib64pulseglib2-16.1-4.x86_64             @cooker-x86_64
    Upgraded      lib64pulseglib2-16.1-3.x86_64             @@System
    Upgrade       microcode-intel-20220809-1.noarch         @cooker-x86_64
    Upgraded      microcode-intel-20220510-1.noarch         @@System
    Upgrade       pulseaudio-16.1-4.x86_64                  @cooker-x86_64
    Upgraded      pulseaudio-16.1-3.x86_64                  @@System
    Upgrade       pulseaudio-client-config-16.1-4.x86_64    @cooker-x86_64
    Upgraded      pulseaudio-client-config-16.1-3.x86_64    @@System
    Upgrade       pulseaudio-module-bluetooth-16.1-4.x86_64 @cooker-x86_64
    Upgraded      pulseaudio-module-bluetooth-16.1-3.x86_64 @@System
    Upgrade       pulseaudio-module-x11-16.1-4.x86_64       @cooker-x86_64
    Upgraded      pulseaudio-module-x11-16.1-3.x86_64       @@System
    Upgrade       pulseaudio-module-zeroconf-16.1-4.x86_64  @cooker-x86_64
    Upgraded      pulseaudio-module-zeroconf-16.1-3.x86_64  @@System
    Upgrade       pulseaudio-utils-16.1-4.x86_64            @cooker-x86_64
    Upgraded      pulseaudio-utils-16.1-3.x86_64            @@System
    Upgrade       python-dnf-4.14.0-1.noarch                @cooker-x86_64
    Upgraded      python-dnf-4.13.0-3.noarch                @@System
    Upgrade       xfce4-pulseaudio-plugin-0.4.4-2.x86_64    @cooker-x86_64-unsupported
    Upgraded      xfce4-pulseaudio-plugin-0.4.4-1.x86_64    @@System
    Reason Change GConf2-3.2.6-15.x86_64                    @cooker-x86_64
    Removed       kernel-desktop-5.19.5-1.x86_64            @@System
Scriptlet output:
   1 awk: cmd. line:3: fatal: invalid character class
   2 awk: cmd. line:3: fatal: invalid character class
   3 Generating grub configuration file ...
   4 Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
   5 Found background: /boot/grub2/themes/OpenMandriva/background.png
   6 Found linux image: /boot/vmlinuz-5.19.8-desktop-1omv4090
   7 Found initrd image: /boot/initrd-5.19.8-desktop-1omv4090.img
   8 fgrep: warning: fgrep is obsolescent; using grep -F
   9 Found linux image: /boot/vmlinuz-5.19.7-desktop-1omv4090
  10 Found initrd image: /boot/initrd-5.19.7-desktop-1omv4090.img
  11 fgrep: warning: fgrep is obsolescent; using grep -F
  12 Found linux image: /boot/vmlinuz-5.19.6-desktop-1omv4090
  13 Found initrd image: /boot/initrd-5.19.6-desktop-1omv4090.img
  14 fgrep: warning: fgrep is obsolescent; using grep -F
  15 Found memtest image: /boot/memtest.bin
  16 Warning: os-prober will be executed to detect other bootable partitions.
  17 Its output will be used to detect bootable binaries on them and create new boot entries.
  18 done
tpgxyz commented 1 year ago

This may be a hint. Do you notice gawk to segfault ? coredumpctl list | grep gawk | wc -l

I noticed that gawk after update to 5.2.0 likes to segfault, and plymouth uses awk to parse theme configs and stuff.

edwardp3 commented 1 year ago 
 ~]$ coredumpctl list | grep gawk | wc -l
0

Just now, Cooker, Xfce, kernel-desktop. Tried to downgrade gawk with dnf, no other version available.

tpgxyz commented 1 year ago

[tpg@omv-rockpro64 ~]$ coredumpctl list | grep gawk | wc -l 12

@edwardp3 please try manually download from https://abf.openmandriva.org/build_lists/214192 and install it

edwardp3 commented 1 year ago

Removed the latest gawk via rpm -e --nodeps installed gawk from above link, no change, still get the three blocks at bootup.


~]$ coredumpctl list | grep gawk | wc -l 12
wc: 12: No such file or directory

coredumpctlis showing a lot of python3.11 crashes.

edwardp3 commented 1 year ago

Just updated system, new kernel-desktop came in (5.19.8-2) and gawk reverted to the previously installed version (5.2.0), no change at bootup.

tpgxyz commented 1 year ago

@edwardp3 Did you regenerated initrd ?

I noticed this in my case:

[tpg@omv-rockpro64 /home/tpg]# plymouth-set-default-theme                                                                                                                                                        
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
text

https://cgit.freedesktop.org/plymouth/tree/scripts/plymouth-set-default-theme.in#n63

and that calls function that wraps awk https://cgit.freedesktop.org/plymouth/tree/scripts/plymouth-set-default-theme.in#n45

This fails and THEME_NAME is empty so plymouth fallback to text mode and that is why we see that dots

tpgxyz commented 1 year ago

Reverting to gawk-5.1.1 i get this:

[tpg@omv-rockpro64 /home/tpg]# plymouth-set-default-theme                                                                                                                                                        
bgrt
tpgxyz commented 1 year ago

Yes with gawk-5.1.1 plymouth works as expected.

rugyada commented 1 year ago

Downgrade gawk fixed the issue

$ rpm -q gawk
gawk-5.1.1-4.x86_64

Thank you very much.

edwardp3 commented 1 year ago

No, did not initially regenerate initrd. Removed the new gawk, reinstalled 5.1.1, ran plymouth-set-default-theme. This was the output:

$ sudo dnf install gawk-5.1.1-3-omv4090.x86_64.rpm
Last metadata expiration check: 2:38:05 ago on Mon 12 Sep 2022 10:14:24 AM EDT.
Dependencies resolved.
================================================================================
 Package        Architecture     Version           Repository              Size
================================================================================
Installing:
 gawk           x86_64           5.1.1-3           @commandline           1.1 M

Transaction Summary
================================================================================
Install  1 Package

Total size: 1.1 M
Installed size: 2.7 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Installing       : gawk-5.1.1-3.x86_64                                    1/1 
  Running scriptlet: gawk-5.1.1-3.x86_64                                    1/1 
  Verifying        : gawk-5.1.1-3.x86_64                                    1/1 

Installed:
  gawk-5.1.1-3.x86_64                                                           

Complete!
[epp@openmandriva Downloads]$ plymouth-set-default-theme
OpenMandriva
[epp@openmandriva Downloads]$ plymouth-set-default-theme -R OpenMandriva
This program must be run as root
[epp@openmandriva Downloads]$ sudo plymouth-set-default-theme -R OpenMandriva
[epp@openmandriva Downloads]$

Rebooted, OpenMandriva splash successfully displayed. Thank you.

So it's the new gawk version causing this, not the kernel?

rugyada commented 1 year ago

So it's the new gawk version causing this, not the kernel?

Yes.