https://bugs.kde.org/show_bug.cgi?id=471981
Bug ID: 471981
Summary: Can't login to Wayland session anymore
Classification: Plasma
Product: plasmashell
Version: 5.27.5
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Startup process
Assignee: plasma-b...@kde.org
Reporter: sadiyumu...@gmail.com
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
For some time now I've been testing Wayland once a month or so in order to see
the progress made, and if I can switch to it for regular use.
However, the other day I found myself immediately thrown back to SDDM login
screen as if the file "usr/bin/startplasma-wayland" was missing.
The contents of file "~/.local/share/wayland-session.log":
Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
A newly created user can login to Wayland session, and the file
"~/.local/share/wayland-session.log" is empty there. However, after logging out
and repeating my Wayland login failure, that empty log file is also filled with
the same contents as mine after successful Wayland login.
Disabling all startup apps and scripts makes no difference. Adding the same
desktop layout including the same third party widgets as well as startup apps
and scripts doesn't prevent the new user to log in to Wayland session either.
The terminal command "XDG_SESSION_TYPE=wayland dbus-run-session
startplasma-wayland" or "dbus-run-session startplasma-wayland" sometimes
briefly displays black screen and even plays the login sound with the following
output:
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with
status 1
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with
status 1 ' requested by '1.0' (uid=1000 pid=7938 comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1 requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with
status 1
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with
status 1
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with
status 1
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with
status 1
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with
status 1
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.kde.KSplash' requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1' requested by '1.0' (uid=1000 pid=7938
comm="startplasma-wayland")
dbus-daemon [7937]: [session uid=1000 pid=79371 Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with
status 1
dbus-daemon [7937]: [session uid=1000 pid=7937] Activating service
name='org.freedesktop.systemd1' requested by 1.3' (uid=1000 pid=7964
comm="/usr/bin/kwin_wayland_wrapper --xwayland")
dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service
'org.freedesktop.systemdi' failed: Process org.freedesktop.systemdi exited with
status 1
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid=7977, result = 0
No backend specified, automatically choosing drm
The Wayland connection broke. Did the Wayland compositor die?f0 "") unless they
are emitted in the object's thread QThread (0x55ba74a45218
"libinput-connection"). Current thread is QThread(0x55ba749f1b70").handled with
.catch(). To termina
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
Gdk-Message: 17:00:53.965: Lost connection to Wayland compositor.
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Testing
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.8
ADDITIONAL INFORMATION
I also tried to produce a crash report without success.
Running the command "echo export
DEBUGINFOD_URLS=\"https://debuginfod.debian.net\"; | sudo tee -a /etc/profile"
was successful, but the command "echo $DEBUGINFOD_URLS" didn't display
anything.
Nevertheless I went on to run the command "gdb /usr/bin/startplasma-wayland"
but I was warned that there were no debugging symbols available.
The subsequent command produced this terminal output:
(gdb) run /usr/bin/startplasma-wayland
Starting program: /usr/bin/start plasma-wayland /usr/bin/startplasma-wayland
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff05ff6c0 (LWP 2387)]
[Detaching after fork from child process 2389]
[New Thread 0x7fffefc276c0 (LWP 2419)]
[New Thread 0x7fffefc276c0 (LWP 2420)]
[Thread 0x7fffefc276c0 (LWP 2419) exited]
[New Thread 0x7fffef4266c0 (LWP 2421)]
[New Thread 0x7fffee1ab6c0 (LWP 2428)]
[Detaching after fork from child process 2448]
Error: could not determine $DISPLAY.
Error: Can not connect kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255
[Thread 0x7fffee1ab6c0 (LWP 2428) exited]
[Thread 0x7fffef4266c0 (LWP 2421) exited]
[Thread 0x7fffefc276c0 (LWP 2420) exited]
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
[Thread 0x7ffff05ff6c0 (LWP 2387) exited]
[Inferior 1 (process 2384) exited normally]
(gdb)
--
You are receiving this mail because:
You are watching all bug changes.
