KDE splash screen not showing up on login/boot

I recently converted to EndeavourOS after Arch Linux proved to be too overwhelming for a noob like me. Everything works great, but there are a few problems I’ve never had on my Arch install.

Current issue, I have is that no matter how many times I apply a splash screen theme in KDE, it never shows up on login. I can preview them fine on the desktop side, but whenever I login it never shows up and everything just starts from blackness. Weirdly my secondary monitor lights up first and then the main.

Anyone got ideas on how to resolve or what the issue would be?

Welcome to the forum @Psychosis!
Ckeck whether you can log-in to X11 session
yay -S plasma-x11-session
Then xrand shows your monitor / device names.
My primary is eDP. Secondary HDMI-A-0 is on the left.
Created this file (so that to see password dots on primary display):
/etc/X11/xorg.conf.d/10-monitor.conf

# the right one
Section “Monitor”
Identifier “eDP”
Option “Primary” “true”
Option “Enable” “true”
Option “PreferredMode” “1920x1200x60.0”
Option “Broadcast RGB” “Full”
EndSection

# the left one
Section “Monitor”
Identifier “HDMI-A-0”
Option “LeftOf” “eDP”
Option “Primary” “false”
Option “Disable” “true”
Option “Enable” “false”
Option “PreferredMode” “1600x900x60.0”
Option “Broadcast RGB” “Full”
EndSection

Then you may log into wayland.
You see the splash screen AFTER a successful log-in. Idk how fast is your machine.
Tested with

I don’t usually have a splash screen on my KDE but tried it after reading this and nope, it doesn’t work.
Actually tried a few just to make sure. System boots to desktop, no splash screen.

Nopassword option is out of my practice.

journalctl -b 0 | grep splash   
nov 12 19:16:53 owpk ksplashqml[4368]: Using Qt multimedia with FFmpeg version n8.0 GPL version 3 or later
nov 12 19:16:53 owpk ksplashqml[4368]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
nov 12 19:16:53 owpk ksplashqml[4368]: Input #0, matroska,webm, from '/home/a/.local/share/plasma/look-and-feel/LightbulbSplash3DEndeavour/contents/splash/lightbulb-endeavour.webm':
nov 12 19:16:53 owpk ksplashqml[4368]:   Metadata:
nov 12 19:16:53 owpk ksplashqml[4368]:     ENCODER         : Lavf60.16.100
nov 12 19:16:53 owpk ksplashqml[4368]:   Duration: 00:00:09.29, start: 0.000000, bitrate: 18754 kb/s
nov 12 19:16:53 owpk ksplashqml[4368]:   Stream #0:0: Video: vp9 (Profile 2), yuv420p10le(tv, unknown/bt709/iec61966-2-1, progressive), 1300x1080, SAR 1:1 DAR 65:54, 24 fps, 24 tbr, 1k tbn
nov 12 19:16:53 owpk ksplashqml[4368]:     Metadata:
nov 12 19:16:53 owpk ksplashqml[4368]:       ENCODER         : Lavc60.31.102 libvpx-vp9
nov 12 19:16:53 owpk ksplashqml[4368]:       DURATION        : 00:00:09.292000000
nov 12 19:16:54 owpk systemd[1153]: plasma-ksplash.service: Consumed 324ms CPU time, 107.9M memory peak.

This happens to me too, when I get to the desktop with Wayland. With X11, the splash screen animation is usually visible.

In fact, with Wayland, I’ve also noticed another flaw (it also happened with Arch with KDE): if I put some widgets (not third-party ones like the weather or radio, but the default ones you can use with KDE, like the editable widget where you can see the CPU temperature) on the desktop after logging in, the desktop doesn’t load completely, as if it were freezing. In fact, on EOS, the Welcome panel loads, for example, but the menu bar doesn’t. I’m forced to reboot, log in with X11, and remove the widgets. Then I can log back in with Wayland and the desktop works.

This is with the latest versions of KDE, at least 6.5. Up until 6.3 at least, I didn’t have this problem with widgets. The splash screen problem did. I think it’s a bit of a KDE bug.

There must be something else going on because the CPU, memory, network speed, disk usage, and one configured for my graphics card work fine here with the latest Plasma and Wayland.

It could be, but it only happens when I put these widgets on the desktop.

Now I’m left with only two third-party widgets, the radio widget (Advanced Radio Player) and the weather widget (Senua Weather), and it starts up normally. If I add a widget that monitors my CPU temperature, when I reboot with Wayland it freezes. I have to reboot, log in with X11, and remove the widget that monitors the CPU temperature. Then it works fine. It happens on EOS, and it did on Arch. This glitch also happens on Garuda with KDE, sometimes, but usually I just reboot and wait a few seconds at the login screen before logging in, then it works again. It’s a bit strange. Who knows, it might be hardware-related.

I installed Arch with KDE on a mini PC with an integrated Intel graphics card, and so far I haven’t encountered this problem.

On my main computer, however, the one where I have EOS, I also have Debian 13, with KDE 6.3, and with those widgets active on the desktop, and I’ve never had any problems. Different distros, but identical hardware (except for the SSD, all the distros I have are on different disks).

When I tried making this config file, the system just got stuck in bootup. Had to TTY and remove the file

The identifiers of the displays have to be modified according to xrand.
They are different in X11 and in wayland session. You need the ones in X11.