Arch Linux

krs

Member

Registered: 2022-06-18

Posts: 5

[Solved]Plasma 6: Wayland session produces no video output after login

EDIT: This appears to be caused by this nvidia bug. Unplugging my HDMI cable (which is a 2.1 cable plugged into an LG C1) it immediately was able to log in as normal.

So a bit of a weird one here. I upgraded to Plasma 6 today, and it was working just fine initially. But as I was playing around with HDR and the display settings in general, I first noticed that it would keep resetting my display settings every time I rebooted. Then while trying to fix this, after one reboot it would just stop outputting any video when I try to log into Plasma from SDDM. I tried removing the ~/.local/share/kscreen directory but that did not help.

What happens is the SDDM greeter comes up, and after logging in the video output to all my screens stop and doesn't come back on.

I'm using an Nvidia GPU with the proprietary driver.

When logging in, this is printed in the journal:

Mar 07 20:33:00 mainframe sddm-greeter-qt6[1992]: file:///usr/share/sddm/themes/breeze/Main.qml:241:17 Parameter "username" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.
Mar 07 20:33:00 mainframe sddm-greeter-qt6[1992]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
Mar 07 20:33:00 mainframe sddm[927]: Message received from greeter: Login
Mar 07 20:33:00 mainframe sddm[927]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
Mar 07 20:33:00 mainframe sddm[927]: Session "/usr/share/wayland-sessions/plasma.desktop" selected, command: "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" for VT 1
Mar 07 20:33:00 mainframe sddm-helper[2208]: [PAM] Starting...
Mar 07 20:33:00 mainframe sddm-helper[2208]: [PAM] Authenticating...
Mar 07 20:33:00 mainframe sddm-helper[2208]: [PAM] Preparing to converse...
Mar 07 20:33:00 mainframe sddm-helper[2208]: [PAM] Conversation with 1 messages
Mar 07 20:33:00 mainframe sddm-helper[2208]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Mar 07 20:33:00 mainframe sddm-helper[2208]: [PAM] returning.
Mar 07 20:33:00 mainframe sddm[927]: Authentication for user  "krs"  successful
Mar 07 20:33:00 mainframe sddm-helper[2208]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Mar 07 20:33:00 mainframe sddm-helper[2208]: pam_limits(sddm:session): wrong limit value '        unlimited' for limit type '-'
Mar 07 20:33:00 mainframe sddm-helper[2208]: pam_unix(sddm:session): session opened for user krs(uid=1000) by krs(uid=0)
Mar 07 20:33:00 mainframe systemd-logind[875]: New session 7 of user krs.
Mar 07 20:33:00 mainframe systemd[1]: Started Session 7 of User krs.
Mar 07 20:33:00 mainframe sddm-helper[2208]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Mar 07 20:33:00 mainframe sddm-greeter-qt6[1992]: Message received from daemon: LoginSucceeded
Mar 07 20:33:00 mainframe sddm-helper[2214]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Mar 07 20:33:00 mainframe sddm-helper[2208]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Mar 07 20:33:00 mainframe sddm-helper[2216]: Jumping to VT 1
Mar 07 20:33:00 mainframe sddm-helper[2216]: VT mode didn't need to be fixed
Mar 07 20:33:00 mainframe sddm[927]: Session started true
Mar 07 20:33:00 mainframe sddm-helper[1991]: [PAM] Closing session
Mar 07 20:33:00 mainframe sddm-helper[1991]: [PAM] Ended.
Mar 07 20:33:00 mainframe sddm-helper[1991]: pam_unix(sddm-greeter:session): session closed for user sddm
Mar 07 20:33:00 mainframe sddm[927]: Auth: sddm-helper exited successfully
Mar 07 20:33:00 mainframe sddm[927]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Mar 07 20:33:00 mainframe systemd[1]: Starting Locale Service...
Mar 07 20:33:00 mainframe systemd[1]: session-c4.scope: Deactivated successfully.
Mar 07 20:33:00 mainframe systemd[1]: session-c4.scope: Consumed 3.311s CPU time.
Mar 07 20:33:00 mainframe systemd-logind[875]: Session c4 logged out. Waiting for processes to exit.
Mar 07 20:33:00 mainframe systemd-logind[875]: Removed session c4.
Mar 07 20:33:00 mainframe systemd[1]: Started Locale Service.
Mar 07 20:33:00 mainframe systemd[1048]: Reloading requested from client PID 2216 ('startplasma-way')...
Mar 07 20:33:00 mainframe systemd[1048]: Reloading...
Mar 07 20:33:01 mainframe systemd[1048]: Reloading finished in 104 ms.
Mar 07 20:33:01 mainframe systemd[1048]: Created slice Slice /app/dbus-:1.4-org.kde.KSplash.
Mar 07 20:33:01 mainframe systemd[1048]: Started dbus-:1.4-org.kde.KSplash@0.service.
Mar 07 20:33:01 mainframe systemd[1048]: Created slice User Background Tasks Slice.
Mar 07 20:33:01 mainframe systemd[1048]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/krs/.cache/drkonqi/sentry-envelopes/*).
Mar 07 20:33:01 mainframe systemd[1048]: Reached target Session services which should run early before the graphical session is brought up.
Mar 07 20:33:01 mainframe systemd[1048]: Starting KDE Global Shortcuts Server...
Mar 07 20:33:01 mainframe systemd[1048]: Starting KDE Window Manager...
Mar 07 20:33:01 mainframe systemd[1048]: Starting Baloo File Indexer Daemon...
Mar 07 20:33:01 mainframe systemd[1048]: Started KDE Window Manager.
Mar 07 20:33:01 mainframe systemd[1048]: Starting KDE Config Module Initialization...
Mar 07 20:33:01 mainframe systemd[1048]: Starting Splash screen shown during boot...
Mar 07 20:33:01 mainframe systemd[1048]: Started KDE Global Shortcuts Server.
Mar 07 20:33:01 mainframe systemd[1048]: Started Baloo File Indexer Daemon.
Mar 07 20:33:01 mainframe systemd[1048]: Starting Portal service...
Mar 07 20:33:01 mainframe systemd[1048]: Starting flatpak document portal service...
Mar 07 20:33:01 mainframe systemd[1048]: Started flatpak document portal service.
Mar 07 20:33:01 mainframe rtkit-daemon[1015]: Supervising 6 threads of 3 processes of 1 users.
Mar 07 20:33:01 mainframe rtkit-daemon[1015]: Supervising 6 threads of 3 processes of 1 users.
Mar 07 20:33:01 mainframe rtkit-daemon[1015]: Supervising 6 threads of 3 processes of 1 users.
Mar 07 20:33:01 mainframe kwin_wayland[2243]: No backend specified, automatically choosing drm
Mar 07 20:33:01 mainframe kwin_wayland[2243]: OpenGL vendor string:                   NVIDIA Corporation
Mar 07 20:33:01 mainframe kwin_wayland[2243]: OpenGL renderer string:                 NVIDIA GeForce RTX 4070/PCIe/SSE2
Mar 07 20:33:01 mainframe kwin_wayland[2243]: OpenGL version string:                  3.1.0 NVIDIA 550.54.14
Mar 07 20:33:01 mainframe kwin_wayland[2243]: OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Mar 07 20:33:01 mainframe kwin_wayland[2243]: Driver:                                 NVIDIA
Mar 07 20:33:01 mainframe kwin_wayland[2243]: Driver version:                         550.54.14
Mar 07 20:33:01 mainframe kwin_wayland[2243]: GPU class:                              Unknown
Mar 07 20:33:01 mainframe kwin_wayland[2243]: OpenGL version:                         3.1
Mar 07 20:33:01 mainframe kwin_wayland[2243]: GLSL version:                           1.40
Mar 07 20:33:01 mainframe kwin_wayland[2243]: Requires strict binding:                no
Mar 07 20:33:01 mainframe kwin_wayland[2243]: Virtual Machine:                        no
Mar 07 20:33:01 mainframe kwin_wayland[2243]: Timer query support:                    yes
Mar 07 20:33:02 mainframe kernel: sched: RT throttling activated
Mar 07 20:33:05 mainframe kernel: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
Mar 07 20:33:05 mainframe sudo[2294]:      krs : TTY=pts/0 ; PWD=/home/krs ; USER=root ; COMMAND=/usr/bin/journalctl -b --no-pager
Mar 07 20:33:05 mainframe sudo[2294]: pam_unix(sudo:session): session opened for user root(uid=0) by krs(uid=1000)
Mar 07 20:33:05 mainframe sudo[2294]: pam_unix(sudo:session): session closed for user root
Mar 07 20:33:11 mainframe systemd[1]: Stopping User Manager for UID 973...
Mar 07 20:33:11 mainframe systemd[939]: Activating special unit Exit the Session...
Mar 07 20:33:11 mainframe systemd[939]: Stopped target Main User Target.
Mar 07 20:33:11 mainframe systemd[939]: Stopped target Sound Card.
Mar 07 20:33:11 mainframe systemd[939]: Closed Socket to launch DrKonqi for a systemd-coredump crash.
Mar 07 20:33:11 mainframe systemd[939]: Stopping Portal service...
Mar 07 20:33:11 mainframe systemd[939]: Stopping flatpak document portal service...
Mar 07 20:33:11 mainframe systemd[939]: Stopping sandboxed app permission store...
Mar 07 20:33:11 mainframe systemd[939]: Stopped sandboxed app permission store.
Mar 07 20:33:11 mainframe systemd[939]: Stopped Portal service.
Mar 07 20:33:11 mainframe systemd[1]: run-user-973-doc.mount: Deactivated successfully.
Mar 07 20:33:11 mainframe systemd[939]: Stopped flatpak document portal service.
Mar 07 20:33:11 mainframe systemd[939]: Stopped target Basic System.
Mar 07 20:33:11 mainframe systemd[939]: Stopped target Paths.
Mar 07 20:33:11 mainframe systemd[939]: Stopped Submitting pending crash events.
Mar 07 20:33:11 mainframe systemd[939]: Stopped target Sockets.
Mar 07 20:33:11 mainframe systemd[939]: Stopped target Timers.
Mar 07 20:33:11 mainframe systemd[939]: Closed GnuPG network certificate management daemon.
Mar 07 20:33:11 mainframe systemd[939]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 07 20:33:11 mainframe systemd[939]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Mar 07 20:33:11 mainframe systemd[939]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Mar 07 20:33:11 mainframe systemd[939]: Closed GnuPG cryptographic agent and passphrase cache.
Mar 07 20:33:11 mainframe systemd[939]: Closed GnuPG public key management service.
Mar 07 20:33:11 mainframe systemd[939]: Closed p11-kit server.
Mar 07 20:33:11 mainframe systemd[939]: Closed PipeWire PulseAudio.
Mar 07 20:33:11 mainframe systemd[939]: Closed PipeWire Multimedia System Sockets.
Mar 07 20:33:11 mainframe dbus-broker[956]: Dispatched 591 messages @ 1(±2)μs / message.
Mar 07 20:33:11 mainframe systemd[939]: Stopping D-Bus User Message Bus...
Mar 07 20:33:11 mainframe systemd[939]: Stopped D-Bus User Message Bus.
Mar 07 20:33:11 mainframe systemd[939]: Removed slice User Core Session Slice.
Mar 07 20:33:11 mainframe systemd[939]: Closed D-Bus User Message Bus Socket.
Mar 07 20:33:11 mainframe systemd[939]: Removed slice User Application Slice.
Mar 07 20:33:11 mainframe systemd[939]: Reached target Shutdown.
Mar 07 20:33:11 mainframe systemd[939]: Finished Exit the Session.
Mar 07 20:33:11 mainframe systemd[939]: Reached target Exit the Session.
Mar 07 20:33:11 mainframe systemd[1]: user@973.service: Deactivated successfully.
Mar 07 20:33:11 mainframe systemd[1]: Stopped User Manager for UID 973.
Mar 07 20:33:11 mainframe systemd[1]: Stopping User Runtime Directory /run/user/973...
Mar 07 20:33:11 mainframe systemd[1]: run-user-973.mount: Deactivated successfully.
Mar 07 20:33:11 mainframe systemd[1]: user-runtime-dir@973.service: Deactivated successfully.
Mar 07 20:33:11 mainframe systemd[1]: Stopped User Runtime Directory /run/user/973.
Mar 07 20:33:11 mainframe systemd[1]: Removed slice User Slice of UID 973.
Mar 07 20:33:11 mainframe systemd[1]: user-973.slice: Consumed 8.588s CPU time.

The thing that sticks out to me is this:

Mar 07 20:33:05 mainframe kernel: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.

After this it appears to try to continue, but kwin_wayland appears to hang and consume 100% of one CPU core. I also see one nvidia-modeset/kthread_q process consuming 100% of another core. Eventually all the services it tries to start time out and fail.

Then I tried to start the X11 session instead, but that just throws me back to the SDDM login screen again. This is what's in the log after doing so:

Mar 07 20:19:28 mainframe sddm-greeter-qt6[1650]: file:///usr/share/sddm/themes/breeze/Main.qml:241:17 Parameter "username" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.
Mar 07 20:19:28 mainframe sddm-greeter-qt6[1650]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Mar 07 20:19:28 mainframe sddm[927]: Message received from greeter: Login
Mar 07 20:19:28 mainframe sddm[927]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Mar 07 20:19:28 mainframe sddm[927]: Session "/usr/share/xsessions/plasmax11.desktop" selected, command: "/usr/bin/startplasma-x11" for VT 2
Mar 07 20:19:28 mainframe sddm-helper[1969]: [PAM] Starting...
Mar 07 20:19:28 mainframe sddm-helper[1969]: [PAM] Authenticating...
Mar 07 20:19:28 mainframe sddm-helper[1969]: [PAM] Preparing to converse...
Mar 07 20:19:28 mainframe sddm-helper[1969]: [PAM] Conversation with 1 messages
Mar 07 20:19:28 mainframe sddm-helper[1969]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Mar 07 20:19:28 mainframe sddm-helper[1969]: [PAM] returning.
Mar 07 20:19:28 mainframe sddm[927]: Authentication for user  "krs"  successful
Mar 07 20:19:28 mainframe sddm-helper[1969]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Mar 07 20:19:28 mainframe sddm-helper[1969]: pam_limits(sddm:session): wrong limit value '        unlimited' for limit type '-'
Mar 07 20:19:28 mainframe sddm-helper[1969]: pam_unix(sddm:session): session opened for user krs(uid=1000) by krs(uid=0)
Mar 07 20:19:28 mainframe systemd-logind[875]: New session 6 of user krs.
Mar 07 20:19:28 mainframe sddm-greeter-qt6[1650]: Message received from daemon: LoginSucceeded
Mar 07 20:19:28 mainframe systemd[1]: Started Session 6 of User krs.
Mar 07 20:19:28 mainframe sddm-helper[1969]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Mar 07 20:19:28 mainframe sddm-helper[1975]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Mar 07 20:19:28 mainframe sddm-helper[1969]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/bin/startplasma-x11"
Mar 07 20:19:28 mainframe sddm-helper[1977]: Failed to take control of "/dev/tty2" ("root"): Operation not permitted
Mar 07 20:19:28 mainframe sddm[927]: Session started true
Mar 07 20:19:28 mainframe sddm-helper[1969]: [PAM] Closing session
Mar 07 20:19:28 mainframe sddm-helper[1969]: pam_unix(sddm:session): session closed for user krs
Mar 07 20:19:28 mainframe sddm-helper[1969]: [PAM] Ended.
Mar 07 20:19:28 mainframe sddm-helper[1969]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Mar 07 20:19:28 mainframe sddm[927]: Auth: sddm-helper exited with 5
Mar 07 20:19:28 mainframe sddm-helper[1969]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Mar 07 20:19:28 mainframe sddm[927]: Greeter stopping...
Mar 07 20:19:28 mainframe sddm-helper[1649]: Signal received: SIGTERM
Mar 07 20:19:28 mainframe systemd-logind[875]: Session 6 logged out. Waiting for processes to exit.
Mar 07 20:19:29 mainframe sddm-helper[1649]: [PAM] Closing session
Mar 07 20:19:29 mainframe sddm-helper[1649]: pam_unix(sddm-greeter:session): session closed for user sddm
Mar 07 20:19:29 mainframe sddm-helper[1649]: [PAM] Ended.
Mar 07 20:19:29 mainframe sddm[927]: Auth: sddm-helper exited with 255
Mar 07 20:19:29 mainframe sddm[927]: Greeter stopped. SDDM::Auth::HelperExitStatus(255)
Mar 07 20:19:29 mainframe sddm[927]: Socket server stopping...
Mar 07 20:19:29 mainframe sddm[927]: Socket server stopped.
Mar 07 20:19:29 mainframe sddm[927]: Display server stopping...
Mar 07 20:19:29 mainframe systemd[1]: session-c3.scope: Deactivated successfully.
Mar 07 20:19:29 mainframe systemd[1]: session-c3.scope: Consumed 2.129s CPU time.
Mar 07 20:19:29 mainframe systemd-logind[875]: Session c3 logged out. Waiting for processes to exit.
Mar 07 20:19:29 mainframe systemd-logind[875]: Removed session c3.
Mar 07 20:19:29 mainframe sddm[927]: Display server stopped.
Mar 07 20:19:29 mainframe sddm[927]: Running display stop script  QList("/usr/share/sddm/scripts/Xstop")
Mar 07 20:19:29 mainframe sddm[927]: Removing display SDDM::Display(0x7fc0fc00dc10) ...
Mar 07 20:19:29 mainframe sddm[927]: Adding new display...
Mar 07 20:19:29 mainframe sddm[927]: Loaded empty theme configuration
Mar 07 20:19:29 mainframe sddm[927]: Xauthority path: "/run/sddm/xauth_SdzjJj"
Mar 07 20:19:29 mainframe sddm[927]: Using VT 2
Mar 07 20:19:29 mainframe sddm[927]: Display server starting...
Mar 07 20:19:29 mainframe sddm[927]: Writing cookie to "/run/sddm/xauth_SdzjJj"
Mar 07 20:19:29 mainframe sddm[927]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_SdzjJj -noreset -displayfd 20
Mar 07 20:19:30 mainframe sddm[927]: Setting default cursor
Mar 07 20:19:30 mainframe sddm[927]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Mar 07 20:19:30 mainframe sddm[927]: Display server started.
Mar 07 20:19:30 mainframe sddm[927]: Socket server starting...
Mar 07 20:19:30 mainframe sddm[927]: Socket server started.
Mar 07 20:19:30 mainframe sddm[927]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
Mar 07 20:19:30 mainframe sddm[927]: Greeter starting...
Mar 07 20:19:30 mainframe sddm-helper[1991]: [PAM] Starting...
Mar 07 20:19:30 mainframe sddm-helper[1991]: [PAM] Authenticating...
Mar 07 20:19:30 mainframe sddm-helper[1991]: [PAM] returning.
Mar 07 20:19:30 mainframe sddm-helper[1991]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=973) by (uid=0)
Mar 07 20:19:30 mainframe systemd-logind[875]: New session c4 of user sddm.
Mar 07 20:19:30 mainframe systemd[1]: Started Session c4 of User sddm.
Mar 07 20:19:30 mainframe sddm-helper[1991]: Writing cookie to "/tmp/xauth_AGLcMU"
Mar 07 20:19:30 mainframe sddm-helper[1991]: Starting X11 session: "" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-SMLsXD --theme /usr/share/sddm/themes/breeze"
Mar 07 20:19:30 mainframe sddm[927]: Greeter session started successfully
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: High-DPI autoscaling Enabled
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Reading from "/usr/local/share/wayland-sessions/plasma.desktop"
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Reading from "/usr/local/share/xsessions/plasmax11.desktop"
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Connected to the daemon.
Mar 07 20:19:30 mainframe sddm[927]: Message received from greeter: Connect
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: QObject: Cannot create children for a parent that is in a different thread.
                                                  (Parent is QGuiApplication(0x7ffe3fac7e10), parent's thread is QThread(0x5e1578c784d0), current thread is QThread(0x5e1578d36900)
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: QObject: Cannot create children for a parent that is in a different thread.
                                                  (Parent is QGuiApplication(0x7ffe3fac7e10), parent's thread is QThread(0x5e1578c784d0), current thread is QThread(0x5e1578d36900)
Mar 07 20:19:30 mainframe wireplumber[1086]: can't open control for card hw:2: No such file or directory
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Adding view for "HDMI-0" QRect(2560,0 3840x2160)
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Adding view for "DP-2" QRect(0,0 2560x1440)
Mar 07 20:19:30 mainframe sddm-greeter-qt6[1992]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Mar 07 20:19:31 mainframe sddm-greeter-qt6[1992]: Adding view for "DP-4" QRect(6400,0 1920x1080)
Mar 07 20:19:31 mainframe sddm-greeter-qt6[1992]: Message received from daemon: Capabilities
Mar 07 20:19:31 mainframe sddm-greeter-qt6[1992]: Message received from daemon: HostName

One thing that seems odd to me in the above is this:

Mar 07 20:19:28 mainframe sddm-helper[1969]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/bin/startplasma-x11"

Why is it "Starting Wayland user session" for startplasma-x11? I haven't actually started the x11 session in quite a while so I'm not sure if this is a new issue unfortunately.

In desperation I've attempted to delete any kde directories and files in my user's home folder in an attempt to reset settings to default, but it has not made any difference. Any help would be appreciated.

Last edited by krs (2024-03-07 20:07:39)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,076

Re: [Solved]Plasma 6: Wayland session produces no video output after login

https://bbs.archlinux.org/viewtopic.php … 1#p2155191 ?

krs

Member

Registered: 2022-06-18

Posts: 5

Re: [Solved]Plasma 6: Wayland session produces no video output after login

Thanks for the tip, that one actually did cause a similar issue for me in the past. But I already removed the kdeglobals file while trying to fix this. But as I wrote in my edit this is actually an nvidia driver issue it seems, when connected to a 4k120 or 8k display:
https://github.com/NVIDIA/open-gpu-kern … issues/484

I'm still a bit perplexed about it seemingly trying to start a wayland session when I selected the X11 session though.

rusty-chip

Member

Registered: 2024-03-08

Posts: 3

Re: [Solved]Plasma 6: Wayland session produces no video output after login

I also encountered the same problem as you. Plasma keeps resetting my display settings every time I rebooted. After modifying some configs associated with kscreen, after one reboot it would just stop outputting any video when I try to log into Plasma from SDDM.
I also have an NVIDIA card in my laptop and a external monitor connected to my laptop. The only way I can find is to use kscreen-doctor to set the display settings manually every time I log in to the plasma.

krs

Member

Registered: 2022-06-18

Posts: 5

Re: [Solved]Plasma 6: Wayland session produces no video output after login

Unfortunately I'm not sure how I solved the part about it resetting my display settings, but that stopped happening once I got past the video output issue. I don't think it was related though. Perhaps in my desperation to reset all KDE settings I managed to delete the correct file. Curiously I still don't have any ~/.local/share/kscreen directory, so I'm not sure where the display settings are saved now in Plasma 6.

The issue with the video output not working though was because of having my TV plugged into the HDMI output set to 2160p @ 120hz. If I keep it at 60hz I don't have the issue, and I can then switch to 120hz once inside Plasma. So if you have a 4k 120hz display plugged in externally try unplugging that if you still don't have any video output.