Arch Linux

treestreet

Member

Registered: 2020-09-05

Posts: 12

[solved]amdgpu is failing to load in to Wayland on sddm

Howdy all. I recently se up a new install of Arch, and I'm having a pretty good experience, at least until yesterday I was. For some reason, I am now now having any luck with getting Wayland to work. When I type in my password, it goes to a black screen, and my monitor stops detecting an output. I installed the plasma x11 session, and I can use my desktop. I restored to a timeshift snapshot that I took on Sunday, and I was able to use Wayland again, I held off on running an system upgrade again wondering if the available package updates I had for. I checked the news page to see if I needed to hold off on upgrading, but I didn't see anything.

I also attempted to paste some system logs into Gemini, and it said that I had a kernel that was too old for my mesa driver. I don't really trust this, as I have the newest kernel in the repos, and I re-ran reflector to check if I had stale mirrors just to be 100% sure.

Here are some pastes that may be helpful:
My system Information:
Ryzen 5 9600x
Radeon RX 9070xt
32 GB of Memory
Here is a more detailed paste of my system info(taken while in the x11 session):
https://0x0.st/Kbo8.txt

Wayland Session Logs:
https://0x0.st/KboP.txt

amdgpu logs:
https://0x0.st/KboZ.txt

Is anyone else having similar issues? I apologize if this isn't the right place to post this...

Last edited by treestreet (2025-09-12 23:42:56)

treestreet

Member

Registered: 2020-09-05

Posts: 12

Re: [solved]amdgpu is failing to load in to Wayland on sddm

Just a quick update, I updated my kernel this morning and the same thing occurred.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,063

Re: [solved]amdgpu is failing to load in to Wayland on sddm

If you promise to no more apply random sed's to your journals that completely break syntax highlighting, I promise to not tell anybody about Chloe and the other petites and their BBCs

There're two AMD GPU devices and

2025-09-09T18:26:21-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes
2025-09-09T18:40:31-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:53:39-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:55:44-04:00 kernel: amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 150000 tries - optc401_disable_crtc line:230
2025-09-10T05:55:44-04:00 kernel: amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:56:18-04:00 kernel: amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:56:18-04:00 kernel: amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:58:21-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T06:01:30-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes

you've plugged around the outputs?

The last wayand attempt has

2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore4\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore6\" - conversion of \"0,0,0,0\" to QRect failed"

what looks like it's trying to operate on a null output.

Might just be https://wiki.archlinux.org/title/KDE#Un … lution_set but could also indicate that kwin_wayland is trying to operate on the wrong card.

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General (w/ your preferred monitor attachment) and the complete system journal *of that boot* 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

We might have to nudge kwin_wayland into the proper GPU, https://wiki.archlinux.org/title/KDE#Me … -specific)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

treestreet

Member

Registered: 2020-09-05

Posts: 12

Re: [solved]amdgpu is failing to load in to Wayland on sddm

If you promise to no more apply random sed's to your journals that completely break syntax highlighting, I promise to not tell anybody about Chloe and the other petites and their BBCs

There're two AMD GPU devices and

2025-09-09T18:26:21-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes
2025-09-09T18:40:31-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:53:39-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:55:44-04:00 kernel: amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 150000 tries - optc401_disable_crtc line:230
2025-09-10T05:55:44-04:00 kernel: amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:56:18-04:00 kernel: amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:56:18-04:00 kernel: amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T05:58:21-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes
2025-09-10T06:01:30-04:00 kernel: amdgpu 0000:14:00.0: [drm] Cannot find any crtc or sizes

you've plugged around the outputs?

The last wayand attempt has

2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore4\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed"
2025-09-09T18:41:12-04:00 kwin_wayland[927]: kf.config.core: "\"fsrestore6\" - conversion of \"0,0,0,0\" to QRect failed"

what looks like it's trying to operate on a null output.

Might just be https://wiki.archlinux.org/title/KDE#Un … lution_set but could also indicate that kwin_wayland is trying to operate on the wrong card.

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General (w/ your preferred monitor attachment) and the complete system journal *of that boot* 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

We might have to nudge kwin_wayland into the proper GPU, https://wiki.archlinux.org/title/KDE#Me … -specific)

I do have an iGPU in my CPU, but I attempted to plug into my motherboard's displayport, but I'll try the other ports on my GPU.

I'll post logs later today when I get home. Thank you for the advice, and the lesson on systemd file logging 

Last edited by treestreet (2025-09-11 19:05:44)

treestreet

Member

Registered: 2020-09-05

Posts: 12

Re: [solved]amdgpu is failing to load in to Wayland on sddm

Okay. now that I'm home, I did the following:
- Attempted every DisplayPort Port on both the GPU and Motherboard. This did not work.
- Attempted to disabled the iGPU in the BIOS by forcing dGPU only mode to be enabled.
- From a TTY, I ran `/usr/bin/startplasma-wayland`
  - This worked. I am now typing this message from the wayland session.

This narrows the problem down to being an issue related to sddm.

I ran the command you mentioned to get the xorg logs, here's the output:
https://0x0.st/KbJo.txt

I attempted to do the steps you said to nudge kwin, but It still had the issue and I was unable to load the desktop, even using the /usr/bin/startplasma-wayland method.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,063

Re: [solved]amdgpu is failing to load in to Wayland on sddm

That's your journal, the xorg log is a file, https://wiki.archlinux.org/title/Xorg#General describes where to find it.

However, here's the run between a successful login on SDDM, returning to SDDM and logging in on the console

Sep 11 17:55:58 genesis sddm[730]: Authentication for user  "alex"  successful
Sep 11 17:55:58 genesis sddm-greeter-qt6[786]: Message received from daemon: LoginSucceeded
Sep 11 17:55:58 genesis sddm-helper[815]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Sep 11 17:55:58 genesis sddm-helper[815]: pam_unix(sddm:session): session opened for user alex(uid=60174) by alex(uid=0)
Sep 11 17:55:58 genesis systemd-logind[665]: New session 2 of user alex.
Sep 11 17:55:58 genesis systemd[1]: Created slice User Slice of UID 60174.
Sep 11 17:55:58 genesis systemd[1]: Starting User Runtime Directory /run/user/60174...
Sep 11 17:55:58 genesis sddm-helper[771]: [PAM] Closing session
Sep 11 17:55:58 genesis sddm-helper[771]: pam_unix(sddm-greeter:session): session closed for user sddm
Sep 11 17:55:58 genesis sddm-helper[771]: [PAM] Ended.
Sep 11 17:55:58 genesis sddm[730]: Auth: sddm-helper exited successfully
Sep 11 17:55:58 genesis sddm[730]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Sep 11 17:55:58 genesis systemd-logind[665]: Session c1 logged out. Waiting for processes to exit.
Sep 11 17:55:58 genesis systemd[1]: session-c1.scope: Deactivated successfully.
Sep 11 17:55:58 genesis systemd[1]: session-c1.scope: Consumed 187ms CPU time, 92.9M memory peak.
Sep 11 17:55:58 genesis systemd-logind[665]: Removed session c1.
Sep 11 17:55:58 genesis systemd[1]: Finished User Runtime Directory /run/user/60174.
Sep 11 17:55:58 genesis systemd[1]: Starting User Manager for UID 60174...
Sep 11 17:55:58 genesis (systemd)[836]: pam_systemd_home(systemd-user:account): Home for user alex successfully acquired.
Sep 11 17:55:58 genesis (systemd)[836]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[alex] ruser=[<unknown>] rhost=[<unknown>]
Sep 11 17:55:58 genesis (systemd)[836]: pam_unix(systemd-user:session): session opened for user alex(uid=60174) by alex(uid=0)
Sep 11 17:55:58 genesis systemd-logind[665]: New session 3 of user alex.
Sep 11 17:55:58 genesis systemd[836]: Queued start job for default target Main User Target.
Sep 11 17:55:58 genesis systemd-journald[425]: File /var/log/journal/c724116787e74eab9f17e00d8e834964/user-60174.journal corrupted or uncleanly shut down, renaming and replacing.
Sep 11 17:55:58 genesis systemd[836]: Created slice User Application Slice.
Sep 11 17:55:58 genesis systemd[836]: Started Submitting pending crash events (file monitor).
Sep 11 17:55:58 genesis systemd[836]: Started Cleanup lingering KCrash metadata.
Sep 11 17:55:58 genesis systemd[836]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/alex/.cache/drkonqi/sentry-envelopes/*).
Sep 11 17:55:58 genesis systemd[836]: Reached target Paths.
Sep 11 17:55:58 genesis systemd[836]: Reached target Timers.
Sep 11 17:55:58 genesis systemd[836]: Starting D-Bus User Message Bus Socket...
Sep 11 17:55:58 genesis systemd[836]: Listening on GnuPG network certificate management daemon.
Sep 11 17:55:58 genesis systemd[836]: Listening on Socket to launch DrKonqi for a systemd-coredump crash.
Sep 11 17:55:58 genesis systemd[836]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 11 17:55:58 genesis systemd[836]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 11 17:55:58 genesis systemd[836]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 11 17:55:58 genesis systemd[836]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 11 17:55:58 genesis systemd[836]: Listening on GnuPG public key management service.
Sep 11 17:55:58 genesis systemd[836]: Listening on p11-kit server.
Sep 11 17:55:58 genesis systemd[836]: Listening on PipeWire PulseAudio.
Sep 11 17:55:58 genesis systemd[836]: Listening on PipeWire Multimedia System Sockets.
Sep 11 17:55:58 genesis systemd[836]: Listening on D-Bus User Message Bus Socket.
Sep 11 17:55:58 genesis systemd[836]: Reached target Sockets.
Sep 11 17:55:58 genesis systemd[836]: Reached target Basic System.
Sep 11 17:55:58 genesis systemd[1]: Started User Manager for UID 60174.
Sep 11 17:55:58 genesis systemd[836]: Started Cleanup lingering KCrash metadata.
Sep 11 17:55:58 genesis systemd[1]: Started Session 2 of User alex.
Sep 11 17:55:58 genesis systemd[836]: Starting Update XDG user dir configuration...
Sep 11 17:55:58 genesis sddm-helper[815]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Sep 11 17:55:58 genesis systemd[836]: Finished Update XDG user dir configuration.
Sep 11 17:55:58 genesis systemd[836]: Reached target Main User Target.
Sep 11 17:55:58 genesis systemd[836]: Startup finished in 98ms.
Sep 11 17:55:58 genesis sddm-helper[851]: pam_kwallet5: final socket path: /run/user/60174/kwallet5.socket
Sep 11 17:55:58 genesis sddm-helper[815]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Sep 11 17:55:58 genesis sddm-helper[853]: Jumping to VT 1
Sep 11 17:55:58 genesis sddm-helper[853]: VT mode didn't need to be fixed
Sep 11 17:55:58 genesis sddm[730]: Session started true
Sep 11 17:56:08 genesis sddm-helper[815]: [PAM] Closing session
Sep 11 17:56:08 genesis sddm-helper[815]: pam_systemd_home(sddm:session): Not deactivating home directory of alex, as it is still used.
Sep 11 17:56:08 genesis sddm-helper[815]: pam_unix(sddm:session): session closed for user alex
Sep 11 17:56:08 genesis sddm-helper[815]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session
Sep 11 17:56:08 genesis sddm-helper[815]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Sep 11 17:56:08 genesis sddm-helper[815]: [PAM] Ended.
Sep 11 17:56:08 genesis sddm[730]: Auth: sddm-helper exited with 64
Sep 11 17:56:08 genesis sddm[730]: Socket server stopping...
Sep 11 17:56:08 genesis sddm[730]: Socket server stopped.
Sep 11 17:56:08 genesis sddm[730]: Display server stopping...
Sep 11 17:56:08 genesis systemd-logind[665]: Session 2 logged out. Waiting for processes to exit.
Sep 11 17:56:08 genesis sddm[730]: Display server stopped.
Sep 11 17:56:08 genesis sddm[730]: Running display stop script  QList("/usr/share/sddm/scripts/Xstop")
Sep 11 17:56:08 genesis sddm[730]: Removing display SDDM::Display(0x562d86673550) ...
Sep 11 17:56:08 genesis sddm[730]: Adding new display...
Sep 11 17:56:08 genesis sddm[730]: Loaded empty theme configuration
Sep 11 17:56:08 genesis sddm[730]: Xauthority path: "/run/sddm/xauth_qXAuoO"
Sep 11 17:56:08 genesis sddm[730]: Using VT 2
Sep 11 17:56:08 genesis sddm[730]: Display server starting...
Sep 11 17:56:08 genesis sddm[730]: Writing cookie to "/run/sddm/xauth_qXAuoO"
Sep 11 17:56:08 genesis sddm[730]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_qXAuoO -noreset -displayfd 18
Sep 11 17:56:08 genesis systemd[1]: Stopping User Manager for UID 966...
Sep 11 17:56:08 genesis systemd[775]: Activating special unit Exit the Session...
Sep 11 17:56:08 genesis systemd[775]: Stopped target Main User Target.
Sep 11 17:56:08 genesis systemd[775]: Stopped target Basic System.
Sep 11 17:56:08 genesis systemd[775]: Stopped target Paths.
Sep 11 17:56:08 genesis systemd[775]: Stopped Submitting pending crash events (file monitor).
Sep 11 17:56:08 genesis systemd[775]: Stopped target Sockets.
Sep 11 17:56:08 genesis systemd[775]: Stopped target Timers.
Sep 11 17:56:08 genesis systemd[775]: Closed GnuPG network certificate management daemon.
Sep 11 17:56:08 genesis systemd[775]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 11 17:56:08 genesis systemd[775]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 11 17:56:08 genesis systemd[775]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 11 17:56:08 genesis systemd[775]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 11 17:56:08 genesis systemd[775]: Closed GnuPG public key management service.
Sep 11 17:56:08 genesis systemd[775]: Closed p11-kit server.
Sep 11 17:56:08 genesis systemd[775]: Closed PipeWire PulseAudio.
Sep 11 17:56:08 genesis systemd[775]: Closed PipeWire Multimedia System Sockets.
Sep 11 17:56:08 genesis dbus-broker[791]: Dispatched 190 messages @ 0(±1)μs / message.
Sep 11 17:56:08 genesis systemd[775]: Stopping D-Bus User Message Bus...
Sep 11 17:56:08 genesis systemd[775]: Stopped D-Bus User Message Bus.
Sep 11 17:56:08 genesis systemd[775]: Removed slice User Core Session Slice.
Sep 11 17:56:08 genesis systemd[775]: Closed D-Bus User Message Bus Socket.
Sep 11 17:56:08 genesis systemd[775]: Removed slice User Application Slice.
Sep 11 17:56:08 genesis systemd[775]: Reached target Shutdown.
Sep 11 17:56:08 genesis systemd[775]: Finished Exit the Session.
Sep 11 17:56:08 genesis systemd[775]: Reached target Exit the Session.
Sep 11 17:56:08 genesis systemd-logind[665]: Removed session 1.
Sep 11 17:56:08 genesis (sd-pam)[777]: pam_unix(systemd-user:session): session closed for user sddm
Sep 11 17:56:08 genesis systemd[1]: user@966.service: Deactivated successfully.
Sep 11 17:56:08 genesis systemd[1]: Stopped User Manager for UID 966.
Sep 11 17:56:08 genesis systemd[1]: Stopping User Runtime Directory /run/user/966...
Sep 11 17:56:08 genesis systemd[1]: run-user-966.mount: Deactivated successfully.
Sep 11 17:56:08 genesis systemd[1]: user-runtime-dir@966.service: Deactivated successfully.
Sep 11 17:56:08 genesis systemd[1]: Stopped User Runtime Directory /run/user/966.
Sep 11 17:56:08 genesis systemd[1]: Removed slice User Slice of UID 966.
Sep 11 17:56:08 genesis systemd[1]: user-966.slice: Consumed 291ms CPU time, 104M memory peak.
Sep 11 17:56:09 genesis sddm[730]: Setting default cursor
Sep 11 17:56:09 genesis sddm[730]: Could not setup default cursor
Sep 11 17:56:09 genesis sddm[730]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Sep 11 17:56:09 genesis sddm[730]: Display server started.
Sep 11 17:56:09 genesis sddm[730]: Socket server starting...
Sep 11 17:56:09 genesis sddm[730]: Socket server started.
Sep 11 17:56:09 genesis sddm[730]: Loaded empty theme configuration
Sep 11 17:56:09 genesis sddm[730]: Greeter starting...
Sep 11 17:56:09 genesis sddm-helper[924]: [PAM] Starting...
Sep 11 17:56:09 genesis sddm-helper[924]: [PAM] Authenticating...
Sep 11 17:56:09 genesis sddm-helper[924]: [PAM] returning.
Sep 11 17:56:09 genesis sddm-helper[924]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=966) by (uid=0)
Sep 11 17:56:09 genesis systemd-logind[665]: New session c2 of user sddm.
Sep 11 17:56:09 genesis systemd[1]: Created slice User Slice of UID 966.
Sep 11 17:56:09 genesis systemd[1]: Starting User Runtime Directory /run/user/966...
Sep 11 17:56:09 genesis systemd[1]: Finished User Runtime Directory /run/user/966.
Sep 11 17:56:09 genesis systemd[1]: Starting User Manager for UID 966...
Sep 11 17:56:09 genesis (systemd)[927]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[sddm] ruser=[<unknown>] rhost=[<unknown>]
Sep 11 17:56:09 genesis (systemd)[927]: pam_unix(systemd-user:session): session opened for user sddm(uid=966) by sddm(uid=0)
Sep 11 17:56:09 genesis systemd-logind[665]: New session 4 of user sddm.
Sep 11 17:56:09 genesis systemd[927]: Queued start job for default target Main User Target.
Sep 11 17:56:09 genesis systemd[927]: Created slice User Application Slice.
Sep 11 17:56:09 genesis systemd[927]: Started Submitting pending crash events (file monitor).
Sep 11 17:56:09 genesis systemd[927]: Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini).
Sep 11 17:56:09 genesis systemd[927]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/drkonqi/sentry-envelopes/*).
Sep 11 17:56:09 genesis systemd[927]: Reached target Paths.
Sep 11 17:56:09 genesis systemd[927]: Reached target Timers.
Sep 11 17:56:09 genesis systemd[927]: Starting D-Bus User Message Bus Socket...
Sep 11 17:56:09 genesis systemd[927]: Listening on GnuPG network certificate management daemon.
Sep 11 17:56:09 genesis systemd[927]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Sep 11 17:56:09 genesis systemd[927]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 11 17:56:09 genesis systemd[927]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 11 17:56:09 genesis systemd[927]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 11 17:56:09 genesis systemd[927]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 11 17:56:09 genesis systemd[927]: Listening on GnuPG public key management service.
Sep 11 17:56:09 genesis systemd[927]: Listening on p11-kit server.
Sep 11 17:56:09 genesis systemd[927]: Listening on PipeWire PulseAudio.
Sep 11 17:56:09 genesis systemd[927]: Listening on PipeWire Multimedia System Sockets.
Sep 11 17:56:09 genesis systemd[927]: Listening on D-Bus User Message Bus Socket.
Sep 11 17:56:09 genesis systemd[927]: Reached target Sockets.
Sep 11 17:56:09 genesis systemd[927]: Reached target Basic System.
Sep 11 17:56:09 genesis systemd[927]: Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini).
Sep 11 17:56:09 genesis systemd[1]: Started User Manager for UID 966.
Sep 11 17:56:09 genesis systemd[927]: Starting Update XDG user dir configuration...
Sep 11 17:56:09 genesis systemd[1]: Started Session c2 of User sddm.
Sep 11 17:56:09 genesis sddm-helper[924]: Writing cookie to "/tmp/xauth_RzVsPz"
Sep 11 17:56:09 genesis sddm-helper[924]: Starting X11 session: "" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-LZfyvh"
Sep 11 17:56:09 genesis sddm[730]: Greeter session started successfully
Sep 11 17:56:09 genesis systemd[927]: Finished Update XDG user dir configuration.
Sep 11 17:56:09 genesis systemd[927]: Reached target Main User Target.
Sep 11 17:56:09 genesis systemd[927]: Startup finished in 96ms.
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: High-DPI autoscaling Enabled
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Reading from "/usr/local/share/wayland-sessions/plasma.desktop"
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Reading from "/usr/local/share/xsessions/plasmax11.desktop"
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Reading from "/usr/share/xsessions/plasmax11.desktop"
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Loading theme configuration from "qrc:/theme/theme.conf"
Sep 11 17:56:09 genesis systemd[927]: Created slice User Core Session Slice.
Sep 11 17:56:09 genesis systemd[927]: Starting D-Bus User Message Bus...
Sep 11 17:56:09 genesis dbus-broker-launch[942]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Sep 11 17:56:09 genesis dbus-broker-launch[942]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Sep 11 17:56:09 genesis dbus-broker-launch[942]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Sep 11 17:56:09 genesis dbus-broker-launch[942]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Sep 11 17:56:09 genesis dbus-broker-launch[942]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Sep 11 17:56:09 genesis systemd[927]: Started D-Bus User Message Bus.
Sep 11 17:56:09 genesis dbus-broker-launch[942]: Ready
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Connected to the daemon.
Sep 11 17:56:09 genesis sddm[730]: Message received from greeter: Connect
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Loading qrc:/theme/Main.qml...
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: file:///usr/lib/qt6/qml/SddmComponents/LayoutBox.qml:35:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: file:///usr/lib/qt6/qml/SddmComponents/ComboBox.qml:105:9: QML Image: Cannot open: file:///usr/lib/qt6/qml/SddmComponents/angle-down.png
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: qrc:/theme/Main.qml:41:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Adding view for "DisplayPort-0" QRect(0,0 2560x1440)
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Message received from daemon: Capabilities
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: Message received from daemon: HostName
Sep 11 17:56:09 genesis sddm-greeter-qt6[938]: file:///usr/lib/qt6/qml/SddmComponents/PictureBox.qml:106:13 Parameter "event" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.
Sep 11 17:56:09 genesis systemd[1]: Started Getty on tty3.
Sep 11 17:56:09 genesis kernel: fbcon: Taking over console
Sep 11 17:56:09 genesis systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
Sep 11 17:56:09 genesis systemd[1]: Stopped Virtual Console Setup.
Sep 11 17:56:09 genesis systemd[1]: Stopping Virtual Console Setup...
Sep 11 17:56:09 genesis systemd[1]: Starting Virtual Console Setup...
Sep 11 17:56:09 genesis kernel: Console: switching to colour frame buffer device 160x45
Sep 11 17:56:09 genesis systemd[1]: Finished Virtual Console Setup.
Sep 11 17:56:15 genesis systemd-homed[664]: alex: changing state active → authenticating-for-acquire
Sep 11 17:56:15 genesis systemd-homework[971]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
Sep 11 17:56:15 genesis systemd-homed[664]: Authentication failed: Password for home alex is incorrect or not sufficient for authentication.
Sep 11 17:56:15 genesis systemd-homed[664]: alex: changing state authenticating-for-acquire → active
Sep 11 17:56:17 genesis systemd-timesyncd[468]: Contacted time server 96.231.54.40:123 (2.arch.pool.ntp.org).
Sep 11 17:56:17 genesis systemd-timesyncd[468]: Initial clock synchronization to Thu 2025-09-11 17:56:17.264632 EDT.
Sep 11 17:56:17 genesis systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Sep 11 17:56:18 genesis systemd-homed[664]: alex: changing state active → authenticating-for-acquire
Sep 11 17:56:18 genesis systemd-homework[975]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
Sep 11 17:56:21 genesis systemd-homed[664]: Authentication failed: Password for home alex is incorrect or not sufficient for authentication.
Sep 11 17:56:21 genesis systemd-homed[664]: alex: changing state authenticating-for-acquire → active
Sep 11 17:56:23 genesis systemd-homed[664]: alex: changing state active → authenticating-for-acquire
Sep 11 17:56:23 genesis systemd-homework[977]: Provided password unlocks user record.
Sep 11 17:56:23 genesis systemd-homework[977]: Read embedded .identity file.
Sep 11 17:56:23 genesis systemd-homework[977]: Provided password unlocks user record.
Sep 11 17:56:23 genesis systemd-homework[977]: Reconciling embedded user identity completed (host and embedded version were identical).
Sep 11 17:56:23 genesis systemd-homework[977]: Everything completed.
Sep 11 17:56:23 genesis systemd-homed[664]: alex: changing state authenticating-for-acquire → active
Sep 11 17:56:23 genesis login[962]: pam_systemd_home(login:auth): Home for user alex successfully acquired.
Sep 11 17:56:23 genesis login[962]: pam_unix(login:session): session opened for user alex(uid=60174) by alex(uid=0)
Sep 11 17:56:23 genesis systemd-logind[665]: New session 5 of user alex.

The critical part is

Sep 11 17:55:58 genesis systemd[1]: Started Session 2 of User alex.
Sep 11 17:55:58 genesis systemd[836]: Starting Update XDG user dir configuration...
Sep 11 17:55:58 genesis sddm-helper[815]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Sep 11 17:55:58 genesis systemd[836]: Finished Update XDG user dir configuration.
Sep 11 17:55:58 genesis systemd[836]: Reached target Main User Target.
Sep 11 17:55:58 genesis systemd[836]: Startup finished in 98ms.
Sep 11 17:55:58 genesis sddm-helper[851]: pam_kwallet5: final socket path: /run/user/60174/kwallet5.socket
Sep 11 17:55:58 genesis sddm-helper[815]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Sep 11 17:55:58 genesis sddm-helper[853]: Jumping to VT 1
Sep 11 17:55:58 genesis sddm-helper[853]: VT mode didn't need to be fixed
Sep 11 17:55:58 genesis sddm[730]: Session started true
Sep 11 17:56:08 genesis sddm-helper[815]: [PAM] Closing session
Sep 11 17:56:08 genesis sddm-helper[815]: pam_systemd_home(sddm:session): Not deactivating home directory of alex, as it is still used.
Sep 11 17:56:08 genesis sddm-helper[815]: pam_unix(sddm:session): session closed for user alex

because nothing gets started at all here.

Since X11 works it's probably not about homed or the kwallet pam and since the manual /usr/bin/startplasma-wayland works it's also not about kwin_wayland
Can you start a different wayland session (sway, hyprland, …) from SDDM?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

treestreet

Member

Registered: 2020-09-05

Posts: 12

Re: [solved]amdgpu is failing to load in to Wayland on sddm

I just got home. To start, I ran a system upgrade to see if there was any new software. Several KDE packages, related to display and wayland were updated. I rebooted, and had the same thing happen.

I also installed sway, and I had the same problem occur.

treestreet

Member

Registered: 2020-09-05

Posts: 12

Re: [solved]amdgpu is failing to load in to Wayland on sddm

I'm really embarrassed to admit this... But the issue was that I had a screwed up bashrc file. I fixed it, and I no longer have any issues.