[SOLVED] Can't start Plasma Wayland session

Lv101Magikarp · 2022-09-21 20:26:53

Hello,
Usually I mostly use X11, and experiment with Wayland occasionally.
I'm using my Arch installation with Plasma for approximately 3 months now, and back then I tried Wayland and I wasn't able to start a session, sddm just kicked me right back to the login screen. But as I was in the middle of customizing stuff so I didn't look into the issue.
Now I just decided try Wayland again and I still have the same issue.

Here's the output of journalctl -u sddm -b -1:

Sep 21 19:19:59 computer systemd[1]: Started Simple Desktop Display Manager.
Sep 21 19:20:00 computer sddm[591]: Initializing...
Sep 21 19:20:00 computer sddm[591]: Starting...
Sep 21 19:20:00 computer sddm[591]: Logind interface found
Sep 21 19:20:00 computer sddm[591]: Adding new display on vt 1 ...
Sep 21 19:20:00 computer sddm[591]: Loading theme configuration from ""
Sep 21 19:20:00 computer sddm[591]: Display server starting...
Sep 21 19:20:00 computer sddm[591]: Adding cookie to "/var/run/sddm/{fe4d7161-9b67-4eac-a982-0c08266ef803}"
Sep 21 19:20:00 computer sddm[591]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{fe4d7161-9b67-4eac-a982-0c08266ef803} -noreset -displayfd 17
Sep 21 19:20:01 computer sddm[591]: Setting default cursor
Sep 21 19:20:01 computer sddm[591]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Sep 21 19:20:01 computer sddm[591]: Display server started.
Sep 21 19:20:01 computer sddm[591]: Socket server starting...
Sep 21 19:20:01 computer sddm[591]: Socket server started.
Sep 21 19:20:01 computer sddm[591]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
Sep 21 19:20:01 computer sddm[591]: Greeter starting...
Sep 21 19:20:01 computer sddm-helper[606]: [PAM] Starting...
Sep 21 19:20:01 computer sddm-helper[606]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=973) by (uid=0)
Sep 21 19:20:01 computer sddm-helper[606]: [PAM] Authenticating...
Sep 21 19:20:01 computer sddm-helper[606]: [PAM] returning.
Sep 21 19:20:01 computer sddm[591]: Greeter session started successfully
Sep 21 19:20:01 computer sddm[591]: Message received from greeter: Connect
Sep 21 19:21:08 computer sddm[591]: Message received from greeter: Login
Sep 21 19:21:08 computer sddm[591]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Sep 21 19:21:08 computer sddm[591]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Sep 21 19:21:08 computer sddm[591]: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Sep 21 19:21:08 computer sddm-helper[772]: [PAM] Starting...
Sep 21 19:21:08 computer sddm-helper[772]: [PAM] Authenticating...
Sep 21 19:21:08 computer sddm-helper[772]: pam_systemd_home(sddm:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Sep 21 19:21:08 computer sddm-helper[772]: [PAM] Preparing to converse...
Sep 21 19:21:08 computer sddm-helper[772]: [PAM] Conversation with 1 messages
Sep 21 19:21:08 computer sddm-helper[772]: gkr-pam: unable to locate daemon control file
Sep 21 19:21:08 computer sddm-helper[772]: [PAM] returning.
Sep 21 19:21:08 computer sddm-helper[772]: gkr-pam: stashed password to try later in open session
Sep 21 19:21:08 computer sddm-helper[772]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Sep 21 19:21:08 computer sddm[591]: Authenticated successfully
Sep 21 19:21:08 computer sddm-helper[772]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Sep 21 19:21:08 computer sddm-helper[772]: pam_unix(sddm:session): session opened for user user(uid=1000) by (uid=0)
Sep 21 19:21:09 computer sddm[591]: Auth: sddm-helper exited successfully
Sep 21 19:21:09 computer sddm[591]: Greeter stopped.
Sep 21 19:21:09 computer sddm-helper[772]: pam_env(sddm:session): deprecated reading of user environment enabled
Sep 21 19:21:09 computer sddm-helper[772]: gkr-pam: unlocked login keyring
Sep 21 19:21:09 computer sddm-helper[772]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Sep 21 19:21:09 computer sddm-helper[772]: Starting: "/usr/share/sddm/scripts/wayland-session /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Sep 21 19:21:09 computer sddm[591]: Session started
Sep 21 19:21:11 computer sddm-helper[772]: pam_unix(sddm:session): session closed for user user
Sep 21 19:21:11 computer sddm-helper[772]: [PAM] Closing session
Sep 21 19:21:11 computer sddm-helper[772]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Sep 21 19:21:11 computer sddm-helper[772]: [PAM] Ended.
Sep 21 19:21:11 computer sddm-helper[772]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Sep 21 19:21:11 computer sddm[591]: Auth: sddm-helper exited successfully
Sep 21 19:21:11 computer sddm[591]: Socket server stopping...
Sep 21 19:21:11 computer sddm[591]: Socket server stopped.

Also when I try to run startplasma-wayland from a terminal I get a black screen and this error (same error for tty2):

Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.

However I can run weston just fine.

I'm using an NVIDIA GeForce RTX 2060 graphics card with the proprietary driver.

Any ideas?

Last edited by Lv101Magikarp (2022-09-22 17:30:44)

seth · 2022-09-21 21:35:00

Don't filter the journal for a process - the issue is most likely not SDDM but eg. kwin_wayland or something else in these 2 seconds

Sep 21 19:21:09 computer sddm-helper[772]: Starting: "/usr/share/sddm/scripts/wayland-session /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Sep 21 19:21:09 computer sddm[591]: Session started
Sep 21 19:21:11 computer sddm-helper[772]: pam_unix(sddm:session): session closed for user user

V1del · 2022-09-22 07:40:50

Nvidia's proprietary driver requires you've enabled KMS in the driver for any Wayland support to work, did you do that? https://wiki.archlinux.org/title/NVIDIA … de_setting

Lv101Magikarp · 2022-09-22 17:29:10

V1del wrote:

Nvidia's proprietary driver requires you've enabled KMS in the driver for any Wayland support to work, did you do that? https://wiki.archlinux.org/title/NVIDIA … de_setting

No I hadn't done that. It turns out setting the nvidia_drm.modeset=1 kernel parameter did indeed fix the issue. Thanks!

Arch Linux

#1 2022-09-21 20:26:53

[SOLVED] Can't start Plasma Wayland session

#2 2022-09-21 21:35:00

Re: [SOLVED] Can't start Plasma Wayland session

#3 2022-09-22 07:40:50

Re: [SOLVED] Can't start Plasma Wayland session

#4 2022-09-22 17:29:10

Re: [SOLVED] Can't start Plasma Wayland session

Board footer