Bug 456101

Summary:	[SOLVED] 'org.kde.KSplash' failed: Process org.kde.KSplash received signal 1
Product:	[Unmaintained] ksplash	Reporter:	Dan <dan76>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	5.25.2
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Dan 2022-06-29 00:40:10 UTC

Plasma starts perfectly when using X11, but when I try to use Wayland it fails with the following:

dbus-daemon[760]: [session uid=501 pid=760] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=501 pid=761 comm="/usr/local/kde5/bin/startplasma-wayland")
No backend specified through command line argument, trying auto resolution
dbus-daemon[760]: [session uid=501 pid=760] Reloaded configuration
dbus-daemon[760]: [session uid=501 pid=760] Reloaded configuration
dbus-daemon[760]: [session uid=501 pid=760] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash received signal 1
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
kdeinit5: Communication error with launcher. Exiting!

Operating System: Linux
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.4
Kernel Version: 5.18.7 (64-bit)
Graphics Processor: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2

Any idea how I can debug this? Thanks!

Comment 1 Dan 2022-08-04 10:03:31 UTC

In the end it was the DISPLAY environment variable that was preventing wayland from starting. If DISPLAY or WAYLAND_DISPLAY is set, Kwin will not use the DRM backend, so I'm closing this as "NOT A BUG".