KDE Wayland login loop after latest update

Desktop Environments Plasma
1

After latest update my system does not get past SDDM login screen if I try to boot normally. Just loops back to SDDM login. With Weston I can get to a desktop of sorts, perhaps a blank desktop is Weston default? Here I can at least open Brave and access the forum to paste these logs.

inxi -Fxxc0z
System:
Kernel: 6.17.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Desktop: Weston v: 14.0.2 dm: SDDM Distro: EndeavourOS base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: B550M-ITX/ac serial:
UEFI: American Megatrends LLC. v: L3.61 date: 04/14/2025
CPU:
Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64
type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 495 min/max: 495/4601 boost: enabled cores: 1: 495
2: 495 3: 495 4: 495 5: 495 6: 495 7: 495 8: 495 9: 495 10: 495 11: 495
12: 495 13: 495 14: 495 15: 495 16: 495 bogomips: 146922
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT
/ 6900 XT] vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-2 pcie:
speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1, DP-2, DP-3,
HDMI-A-1, Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:73bf
Device-2: Advanced Micro Devices [AMD/ATI] Cezanne [Radeon Vega Series /
Radeon Mobile Series] driver: amdgpu v: kernel arch: GCN-5 pcie:
speed: 8 GT/s lanes: 16 ports: active: DP-4 empty: DP-5,HDMI-A-2
bus-ID: 09:00.0 chip-ID: 1002:1638 temp: 31.0 C

Boot log

loka 12 11:11:07 H1 kernel: BIOS-provided physical RAM map:
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009bfefff] usable
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x0000000009bff000-0x0000000009ffffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20cfff] ACPI NVS
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x000000000a20d000-0x000000000affffff] usable
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000b92fafff] usable
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000b92fb000-0x00000000baa65fff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000baa66000-0x00000000baac5fff] ACPI data
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000baac6000-0x00000000bc1bdfff] ACPI NVS
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000bc1be000-0x00000000bcffefff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000bcfff000-0x00000000bdffffff] usable
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000be000000-0x00000000bfffffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd6fffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000081e2fffff] usable
loka 12 11:11:07 H1 kernel: BIOS-e820: [mem 0x000000081e300000-0x000000083fffffff] reserved
loka 12 11:11:07 H1 kernel: NX (Execute Disable) protection: active
loka 12 11:11:07 H1 kernel: APIC: Static calls initialized
loka 12 11:11:07 H1 kernel: efi: EFI v2.7 by American Megatrends
loka 12 11:11:07 H1 kernel: efi: ACPI=0xbc1a7000 ACPI 2.0=0xbc1a7014 TPMFinalLog=0xbb171000 SMBIOS=0xbce23000 SMBIOS 3.0=0xbce22000 MEMATTR=0xb5de5298 ESRT=0xb7f04918 RNG=0xbaa78f18 INITRD=0xb5587e18 TPMEventLog=0xbaa76018
loka 12 11:11:07 H1 kernel: random: crng init done
loka 12 11:11:07 H1 kernel: efi: Remove mem301: MMIO range=[0xf0000000-0xf7ffffff] (128MB) from e820 map
loka 12 11:11:07 H1 kernel: e820: remove [mem 0xf0000000-0xf7ffffff] reserved
loka 12 11:11:07 H1 kernel: efi: Remove mem302: MMIO range=[0xfd200000-0xfd2fffff] (1MB) from e820 map
loka 12 11:11:07 H1 kernel: e820: remove [mem 0xfd200000-0xfd2fffff] reserved
loka 12 11:11:07 H1 kernel: efi: Remove mem303: MMIO range=[0xfd600000-0xfd6fffff] (1MB) from e820 map
loka 12 11:11:07 H1 kernel: e820: remove [mem 0xfd600000-0xfd6fffff] reserved
loka 12 11:11:07 H1 kernel: efi: Not removing mem304: MMIO range=[0xfea00000-0xfea0ffff] (64KB) from e820 map
loka 12 11:11:07 H1 kernel: efi: Remove mem305: MMIO range=[0xfeb80000-0xfec01fff] (0MB) from e820 map
loka 12 11:11:07 H1 kernel: e820: remove [mem 0xfeb80000-0xfec01fff] reserved
loka 12 11:11:07 H1 kernel: efi: Not removing mem306: MMIO range=[0xfec10000-0xfec10fff] (4KB) from e820 map
loka 12 11:11:07 H1 kernel: efi: Not removing mem307: MMIO range=[0xfec30000-0xfec30fff] (4KB) from e820 map
loka 12 11:11:07 H1 kernel: efi: Not removing mem308: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
loka 12 11:11:07 H1 kernel: efi: Not removing mem309: MMIO range=[0xfed40000-0xfed44fff] (20KB) from e820 map
loka 12 11:11:07 H1 kernel: efi: Not removing mem310: MMIO range=[0xfed80000-0xfed8ffff] (64KB) from e820 map
loka 12 11:11:07 H1 kernel: efi: Not removing mem311: MMIO range=[0xfedc2000-0xfedcffff] (56KB) from e820 map
loka 12 11:11:07 H1 kernel: efi: Not removing mem312: MMIO range=[0xfedd4000-0xfedd5fff] (8KB) from e820 map
loka 12 11:11:07 H1 kernel: efi: Remove mem313: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
loka 12 11:11:07 H1 kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
loka 12 11:11:07 H1 kernel: SMBIOS 3.3.0 present.
loka 12 11:11:07 H1 kernel: DMI: To Be Filled By O.E.M. B550M-ITX/ac/B550M-ITX/ac, BIOS L3.61 04/14/2025
loka 12 11:11:07 H1 kernel: DMI: Memory slots populated: 2/2
loka 12 11:11:07 H1 kernel: tsc: Fast TSC calibration using PIT
loka 12 11:11:07 H1 kernel: tsc: Detected 4591.329 MHz processor
loka 12 11:11:07 H1 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
loka 12 11:11:07 H1 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
loka 12 11:11:07 H1 kernel: last_pfn = 0x81e300 max_arch_pfn = 0x400000000
loka 12 11:11:07 H1 kernel: MTRR map: 6 entries (4 fixed + 2 variable; max 21), built from 9 variable MTRRs
loka 12 11:11:07 H1 kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
loka 12 11:11:07 H1 kernel: e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
loka 12 11:11:07 H1 kernel: last_pfn = 0xbe000 max_arch_pfn = 0x400000000
loka 12 11:11:07 H1 kernel: esrt: Reserving ESRT space from 0x00000000b7f04918 to 0x00000000b7f049a0.
loka 12 11:11:07 H1 kernel: e820: update [mem 0xb7f04000-0xb7f04fff] usable ==> reserved
loka 12 11:11:07 H1 kernel: Using GB pages for direct mapping

I also tried to open the eos-log-tool but got this error in terminal

eos-log-tool

(yad:103523): Gtk-WARNING **: 14:56:30.209: cannot open display:

What should be my next step?

2

Might have figured out the root cause. I logged in with tty and tried to run startx. It works, but only partially loads desktop. Basically only some window frames.

I then went back to tty and tried to run plasmashell and got an error:

qt.qpa.xcb: could not connect to display

qt.qpa.plugin: from 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin..

Telling me Qt platform plugin could not be intilialized and reinstalling the application may fix the problem. Also gives me available platform plugins

I’ll post the full error message later.

3

OK, I managed to boot into my system after installing plasma x11 session. However I cannot move any of my windows, there are not window frames or the top bar to grab. Also the window menus seem to overlap my plasma panel. The plasma panel works when visible. Mouse clicking works. Some keybinds don’t work but some do, but the default plasma shortcuts seem to be working for the most part. Something very odd is going on.

Trying to log in to the wayland session still loops back to SDDM login.

Since I’m now able to boot into my system, here’s some output from eos-log-tool:

https://termbin.com/jvyo

4

That sounds like a corrupt config file, try renaming ~/.config/plasmarc and logging in again.

5

This did not change any of the DE behaviour.

I’ve also discovered that the only way I can access the DE is through latest kernel fall back and logging in with the x11 session. This would be fine if I could move windows around, though wayland was great and more reliable than x11.

6

Hmm, there was a recent kwin update, maybe that is causing problems. You can downgrade it using the downgrade program. Run sudo downgrade kwin and pick the previous version, then reboot.

7

Try logging in as another user using the same DE maybe? That would likely tell us if this is a config issue.

1 Like
8

I normally think of that, but it didn’t even cross my mind :scream:

9

Sadly kwin downgrade or logging as another user doesn’t work. Same symptoms.

When I try to “startplasma-wayland” in tty I get:

kf.config.core: “KonfigIni: In file /usr/share/applications/brave.browser.desktop, line 1: “Invalid entey (missing ‘=’)

kf.service.services: The desktop entry file “/usr/share/applications/brave.browser.desktop” does not ahave a “Type=Application” set.

Org.kde.startup: could not start systemd managed Plasma session: “org.freedesktop.systemd1.TransactionDestructive” “Trabsaction for plasma-workspace-wayland.target/start is destructive (graphical.session.target has ‘stop’ job queued, but ‘start’ is included in transaction). “

Error’ Can’t open display:

org.kde.startup: “xmessage” Qlist(“-geometry”, “500x100”, “startkde: Could not start Plasma session. \n”) exited with code 1

startkde: Could not start Plasma session.

10

So far I’ve tried downgrading pretty much everything from kernels, plasma, kwin, sddm… you name it.

Attempting a Timeshift restore. Sadly it’s an old backup from September.

11

Well I saw you are running something called Weston, and from what I understand from the link it runs both on Wayland as well as X11. Not knowing this Weston “thing” I was wondering maybe something is going wrong there ?

12

Don’t even remember why I have Weston, but it was there before this issue and did not affect plasma-wayland.

13

Yes but what I am trying to say is that the last update of the package was about 2 months ago, a lot of updates will probably happen during those 2 months that could “brake” Weston, because of a outdated (so to speak) dependency, or something like that. Could ofcourse have been the latest update too.

14

I eliminated that variable. Weston is no longer installed. To make sure I still ahve a compositor I reinstalled kwin too. Did not fix the issue.

Something is still causing a no display error for wayland.

15

jurnalctl | grep kwin_wayland_wrapper gives this error:

kwin_wayland_wrapper[1947]: /usr/bin/kwin_wayland: error while loading shared libraries: libdisplay-info.so.3: cannot open shared object file: No such file or directory

16

Not sure this will solve your problem but I found this package installed on my end.

17

Looks like you can try to reinstall libdisplay-info.

18

Already did. Did not fix the issue.

19

Ran updates again. There weren’t many, but linux-core was one of the available ones. Updated and rebooted. System boots to DE normally.

What did we learn? Nothing really. :thinking: But the main thing is that this issue is now solved. Thank you all for the suggestions.

Now, excuse me while I go back up all my data before anything breaks again.

20

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.