No pixels between grub and sddm, where's plymouth

English Install/Boot/Login
1

I did an zypper dup from 15.6 to 16.0, so my guess is that I’m just missing something. Isn’t obvious what though.

systemctl status plymouth-start
● plymouth-start.service - Show Plymouth Boot Screen
    Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static)
    Active: active (exited) since Thu 2025-10-02 07:57:01 PDT; 11min ago
Invocation: fdbcedfab981457b964bf2555fe0dd65
   Process: 1164 ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS)
   Process: 1175 ExecStartPost=/usr/bin/plymouth show-splash (code=exited, status=0/SUCCESS)
  Main PID: 739 (code=exited, status=0/SUCCESS)
       CPU: 15ms
2

How? Please provide details.
FWIW 16.0 is a major release. It implies some fundamental changes in the system, f.e. repo coniguration.

3

I’d say my update went poorly, due to cdn.opensuse.org being down and out of date when it’s up. But I really do have openSUSE 16.0 installed now.

The openSUSE Zypper service is actually very insistent on using cdn.opensuse.org and also in updating your repo set to the current release. So I doubt that’s there’s a problem there. My guess is a missing package or a configuration file that’s off.

4

You may want to explain your question or problem so that others can also understand it. We are not staying behind your shoulder and do not see what you are seeing.

5

What do you mean by “your repo set”? Please show zypper lr -d as preformatted text ( the </> in the editor

6

Given the title of this post, I presume this is the one you are looking for: 1248507 – plymouth bootsplash is disabled as default installation. Plymouth bootsplash is disabled in Leap 16.0 as default installation.

7

I didn’t realize everyone wasn’t understanding my question. Yes that’s the bug I’m experiencing exactly.

Gotta say, it doesn’t make much sense that “splash=silent” enables Plymouth. :sweat_smile:

8

Agreed. Given the discussion (and ignorance of the guys in charge) in this bug report lead to the decision to not update our systems to Leap 16.0 and to look for an alternative outside of openSUSE.

9

According to the bug report linked from the mentioned bug report the change in YaST Bootloader happened in Leap 15.1. I wonder, how this parameter appeared in Leap 15 installations then.

1 Like
10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.