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)
If this is still happening, can you see if kwin_wayland is crashing by looking at the output of `coredumpctl --reverse`? If you see a kwin_wayland crash, please attach a backtrace of it that was generated from using `coredumpctl gdb kwin_wayland` Hopefully you can also install debug symbols for kwin manually if debuginfod isn't working in Debian for some reason. Thanks!
This time I experienced something new: Although SDDM still refuses to launch a Wayland session for me (but not any other newly created user), when I switched to terminal with Ctrl+Alt+F3 from SDDM login screen, and entered the command "XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland" I was surprised to find myself in a Wayland session with all my startup apps, customization, settings etc. working - except the panels! I don't know if it's the right thing to do, but I then went on using the Meta key to launch Konsole. The command "echo $DEBUGINFOD_URLS" successfully displayed "https://debuginfod.debian.net" this time, and the command "gdb /usr/bin/startplasma-wayland" also worked, asking "Enable debuginfod for this session? (y or [n])", and then "Downloading separate debug info for" many items. This was followed with the following (slightly abbreviated) terminal output: [New Thread 0x7ffff03ff6c0 (LWP 12161)] [Detaching after fork from child process 12163] [Detaching after fork from child process 12183] kdeinit5: Shutting down running client. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 12217, result = 0 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: opened connection to :1 Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so" Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_mouse.so" Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_style.so" org.kde.plasma.session: process job "kcminit_startup" finished with exit code 0 Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_touchpad.so" Initializing "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_kgamma.so" Xlib XKB extension major= 1 minor= 0 kde.xembedsniproxy: failed to claim ownership of Systray Manager kde.dbusmenuproxy: Failed to register DBus service "org.kde.plasma.gmenu_dbusmenu_proxy" Themes not available. Install qt-material if you want to change GUI's appearance: pip3 install qt-material. Checking screens: available: (QScreen(0x555555658770, name="eDP-1")) redundant: QHash((QScreen(0x55555565a930, name="DP-1"), QScreen(0x555555658770, name="eDP-1"))) fake: QSet() all: (QScreen(0x55555565a930, name="DP-1"), QScreen(0x555555658770, name="eDP-1")) DevTools listening on ws://127.0.0.1:38887/devtools/browser/8f4a80ad-0825-4467-b105-821d25f7b006 DesktopNotifications not available (install python3-notify2): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. exception loading ipasn db: No module named 'pyasn' Install python3-pyasn to display IP's network name. DesktopNotifications not available (install python3-notify2): org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. I then opened a new tab in Konsole and entered the command "coredumpctl --reverse" which displayed the following (TIME and SIZE columns removed), with no kwin_wayland crash: PID UID GID SIG COREFILE EXE 7346 1000 1000 SIGTRAP present /walc 6241 1000 1000 SIGABRT present /tmp/.mount_WALC3wzHqC/walc 6211 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 6183 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 6179 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 6139 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 6095 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 6089 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 5807 1000 1000 SIGABRT present /usr/lib/insync/insync 6057 1000 1000 SIGABRT present /usr/bin/plasmashell 6059 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 6020 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 6018 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 5923 1000 1000 SIGABRT present /usr/bin/plasmashell 5973 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 5908 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 5640 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 5662 1000 1000 SIGABRT present /usr/bin/python3.11 5831 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 5650 1000 1000 SIGABRT present /usr/bin/kaccess 5620 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd 5635 1000 1000 SIGABRT present /usr/bin/plasmashell 5632 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 5672 1000 1000 SIGABRT present /usr/bin/kup-daemon 5643 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 5565 1000 1000 SIGABRT present /usr/bin/ksmserver 5563 1000 1000 SIGABRT present /usr/bin/kded5 3693 0 0 SIGABRT present /usr/libexec/packagekitd 4310 1001 1001 SIGSYS present /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner 4232 1001 1001 SIGSYS present /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner Then I tried starting a Wayland session with default desktop layout/panel settings(replacing the contents of "~/.config/plasma-org.kde.plasma.desktop-appletsrc" and "~/config/plasmashellrc") which worked only from terminal ("XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland"), but not from SDDM login screen. Finally I tried by restoring the contents of "~/.config/plasma-org.kde.plasma.desktop-appletsrc" and "~/config/plasmashellrc", and it worked; I had a fully working Wayland session, but only from terminal, not from SDDM login screen.
If you run XDG_SESSION_TYPE=wayland dbus-run-session kwin_wayland --exit-with-session=konsole do you see a konsole window? --- dbus-daemon [7937]: [session uid=1000 pid=7937] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemdi exited with status 1 system_i_ looks suspicious. Did you modify any system files?
Does it work if you fully shut down instead of logging out? If so, the issue is stale processes not being cleaned up properly, and will probably be fixed by the impending fix for Bug 473824.
(In reply to Vlad Zahorodnii from comment #3) 1. Yes, a Konsole window did open. 2. I might have modified several system files, but I don't think they're related with this, and the fact that I can log in to a Wayland session when I create a new user might support this assumption.
(In reply to Nate Graham from comment #4) No, it behaves exactly the same after I log out, or restart, or shut down the computer. It seems the problem is somewhere in my home directory (maybe a user configuration file in ~/.config directory?) but I can't think of anything that I've made there which might prevent launching a Wayland session...
Can you diff the output of `env` when run in your normal user vs a new user where it works?
(In reply to Nate Graham from comment #7) Below is the output of `diff Env-NewUser.txt Env-Me.txt`. I sorted the text alphabetically, and removed differences of user name and id in order to simplify the comparison. 0a1 > CLUTTER_IM_MODULE=ibus 9a11,12 > GTK_IM_MODULE=ibus > GTK_MODULES=gail:atk-bridge 12,13c15,17 < INVOCATION_ID=a59daf71f3094834bd645a3672d3fda9 < JOURNAL_STREAM=8:387821 --- > IM_CONFIG_PHASE=1 > INVOCATION_ID=37ca9e6b1c58415585b66ba928d126ad > JOURNAL_STREAM=8:27510 14a19 > KDE_FORK_SLAVES=1 18c23 < KONSOLE_DBUS_SERVICE=:1.39 --- > KONSOLE_DBUS_SERVICE=:1.92 38,39c43,44 < MANAGERPID=37900 < MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service/memory.pressure --- > MANAGERPID=1396 > MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kglobalaccel.service/memory.pressure 40a46 > MOZ_USE_XINPUT2=1 44a51,52 > PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket > PAPERSIZE=a4 50a59,60 > QT_EXCLUDE_GENERIC_BEARER=1 > QT_IM_MODULE=ibus 52d61 < SESSION_MANAGER=local/Kdebian:@/tmp/.ICE-unix/38040,unix/Kdebian:/tmp/.ICE-unix/38040 54c63 < SHELL_SESSION_ID=4363399071c7460299a95587a4e59369 --- > SHELL_SESSION_ID=1371aac3e41d4f319eee902e3a7c08a1 56,58c65,67 < SSH_AGENT_PID=37968 < SSH_AUTH_SOCK=/tmp/ssh-RKJrPtE0vVb7/agent.37930 < SYSTEMD_EXEC_PID=38083 --- > SSH_AGENT_PID=1469 > SSH_AUTH_SOCK=/tmp/ssh-hiKLb8oiPlMX/agent.1416 > SYSTEMD_EXEC_PID=1714 61,62c70,71 < WINDOWID=52428813 < XAUTHORITY=/tmp/xauth_FHdwYK --- > WINDOWID=96469005 > XAUTHORITY=/tmp/xauth_tQLYBE 66a76 > XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share/:/usr/share/ 72,73c82,83 < XDG_SESSION_ID=71 < XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session32 --- > XDG_SESSION_ID=1 > XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0 75a86 > XMODIFIERS=@im=ibus
Things that look suspicious to me: QT_IM_MODULE=ibus XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share/:/usr/share/ XMODIFIERS=@im=ibus Can you try unsetting those in your user's environment and trying again?
(In reply to Nate Graham from comment #9) I removed those 3 lines from "~/.config/environment.d/user.conf", and restarted the computer, but nothing changed unfortunately.
Hmm, thanks anyway. Not sure how to proceed here, then. I'll hand it off to someone else.
(In reply to Nate Graham from comment #11) Thanks... I'll also continue trying to find what's getting in the way of SDDM while it's possible to log into Wayland from the command line. It's not a priority for me though as Wayland is still very far from being ready for my daily use.
Ok, let us know if and when you're able to provide the requested info. Thanks!
(In reply to Nate Graham from comment #13) > Ok, let us know if and when you're able to provide the requested info. > Thanks! Oh, I think I did provide the requested info above...or did I miss anything?
Yes, thanks. Sorry about that.
Closing as this is not really actionable and because >2. I might have modified several system files, but I don't think they're related with this, and the fact that I can log in to a Wayland session when I create a new user might support this assumption.