Bugzilla – Bug 1222013
Unable to login using Wayland after OS update.
Last modified: 2024-04-08 23:36:53 UTC
STEPS TO REPRODUCE 1. Set `kcmshell6 kcm_sddm` to https://forums.opensuse.org/uploads/default/original/2X/9/90badc3f0db5d3a3f697fcd7770208133305dbb8.png — "Plasma (Wayland)". 1. Updated to cpe:/o:opensuse:tumbleweed:20240321. 1. Initialized computer via WOL. OBSERVED RESULT Automatic login failed: I saw a TTY, which waited some seconds with an underscore. Afterward, briefly saw dmesg output containing $DISPLAY initialization failure message. Switching to X in SDDM permitted login. Investigation showed journalctl filled with `-p` 1-4 errors. For reference, no priority 1-2 errors were present in journalctl in the immediately previous boot. EXPECTED RESULT I should be able to login via Wayland. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240321 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: llvmpipe Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION https://forums.opensuse.org/t/unable-to-login-with-wayland-not-x-after-update/173564
Created attachment 873826 [details] journalctl traces and error logs from priority 1 to 3. 27 MiB file of 717 kwin_wayland stack traces + 1400+ platform plugin load errors.
(In reply to roke beedell from comment #0) https://bugs.kde.org/show_bug.cgi?id=484536#c0
*** Bug 1221985 has been marked as a duplicate of this bug. ***
Looks like Mesa is broken... What was the previous working snapshot?
(In reply to Fabian Vogt from comment #4) > Looks like Mesa is broken... > > What was the previous working snapshot? Whichever was right before it, to my knowledge. Certainly cpe:/o:opensuse:tumbleweed:20240320, per https://github.com/cyanfish/naps2/issues/335#issue-2202975276.
I don't see any relevant change in 20240321. Autologin into Plasma (Wayland) is known broken, caused by systemd (see https://github.com/sddm/sddm/pull/1896). It it just by chance that you're only hitting that after the upgrade? That is only visible in sddm logs though and usually doesn't even reach kwin_wayland. "kwin_wayland_drm: gbm_create_device() failed" points to a kernel or Mesa issue.
I also am seeing this issue today. I've successfully booted into Plasma 6 Wayland with SDDM before on this machine, so I would be suspicious of recent updates causing this issue. I agree with Fabian that this looks like a Mesa issue. Plasma X11 tells me that my system has fallen back to software rendering, which sounds like my iGPU isn't being used. system details FWIW: Operating System: openSUSE Tumbleweed 20240327 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 31.1 GiB of RAM Manufacturer: LENOVO Product Name: 20XY00BDUS System Version: ThinkPad X1 Yoga Gen 6
(In reply to Loren Burkholder from comment #7) > I also am seeing this issue today. I've successfully booted into Plasma 6 > Wayland with SDDM before on this machine, so I would be suspicious of recent > updates causing this issue. > > I agree with Fabian that this looks like a Mesa issue. Plasma X11 tells me > that my system has fallen back to software rendering, which sounds like my > iGPU isn't being used. Per https://discussion.fedoraproject.org/t/random-indefinite-system-hang/110020, I was getting *lots* of graphical issues, presumably due to Mesa, on the OSTW installation referenced in this issue, so I wouldn't be surprised. However, note that I can't provide NEEDINFOs anymore due to me replacing this installation with a Fedora 40 one in order to ascertain what was OS-specific versus hardware-specific.
I have an update! It turned out to be caused by AMD drivers. I had them installed since I am using an AMD eGPU when I need better graphics than the integrated Intel graphics. Removing the AMD graphics drivers fixed the issue. @roke beedell, you seem to be using AMD graphics as well if I'm not mistaken, which seems to confirm my suspicions. Interestingly, I didn't have to remove kernel-firmware-amdgpu, libdrm_amdgpu1, or libdrm_amdgpu1-32bit for Mesa to start working again.
After some more poking around, I've narrowed it down more specifically to drivers from the amdgpu repo. Drivers from repo-oss work just fine.
(In reply to Loren Burkholder from comment #9) > @roke beedell, you seem to be using AMD graphics as well if I'm not > mistaken, which seems to confirm my suspicions. Yeah, I'm using an XFX AMD Radeon RX 5700 (non-XT).