KDE screen locker hangs when attempting to enter password

I occasionally encounter issues, when my KDE Plasma auto-logs off after some time and I then try to re-log in. In this case, I can enter the password, but hitting enter does not start the log-in. Instead I can still modify the password.

This is my system:

~ >>> inxi --admin --verbosity=8 --filter --no-host --width                                               
System:
  Kernel: 6.12.25-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=4c2ea2f1-3cfa-4377-8778-97f19f2453fe rw quiet
    cryptdevice=UUID=ac37595d-5b67-408c-82b8-547a678e97e6:luks-ac37595d-5b67-408c-82b8-547a678e97e6
    root=/dev/mapper/luks-ac37595d-5b67-408c-82b8-547a678e97e6
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.13.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: MSI product: MS-7798 v: 1.0
    serial: <superuser required>
  Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: 1.9 date: 09/30/2013
Battery:
  Device-1: hidpp_battery_0 model: Logitech M720 Triathlon Multi-Device Mouse
    serial: <filter> charge: 10% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 24 GiB available: 23.4 GiB used: 2.73 GiB (11.7%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 4 modules: 4 EC: None
    max-module-size: 8 GiB note: est.
  Device-1: ChannelA-DIMM0 type: DDR3 detail: synchronous size: 4 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Corsair part-no: CML8GX3M2A1600C9 serial: N/A
  Device-2: ChannelA-DIMM1 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Hynix/Hyundai part-no: HMT41GU6AFR8A-PB serial: <filter>
  Device-3: ChannelB-DIMM0 type: DDR3 detail: synchronous size: 4 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Corsair part-no: CML8GX3M2A1600C9 serial: N/A
  Device-4: ChannelB-DIMM1 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Hynix/Hyundai part-no: HMT41GU6AFR8A-PB serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-3450S bits: 64 type: MCP arch: Ivy Bridge
    gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6
    model-id: 0x3A (58) stepping: 9 microcode: 0x21
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1600 min/max: 1600/3500 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 1600 2: 1600 3: 1600 4: 1600 bogomips: 22409
  Flags: acpi aes aperfmperf apic arat arch_perfmon avx bts clflush cmov
    constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb
    ept erms est f16c flexpriority flush_l1d fpu fsgsbase fxsr ht ibpb ibrs
    ida lahf_lm lm mca mce md_clear mmx monitor msr mtrr nonstop_tsc nopl nx
    pae pat pbe pcid pclmulqdq pdcm pebs pge pln pni popcnt pse pse36 pti pts
    rdrand rdtscp rep_good sep smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
    syscall tm tm2 tpr_shadow tsc tsc_deadline_timer vme vmx vnmi vpid xsave
    xsaveopt xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate]
    vendor: Micro-Star MSI driver: nvidia v: 570.144
    alternate: nouveau,nvidia_drm non-free: 550-570.xx+ status: current (as of
    2025-04; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-2023 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: none off: HDMI-A-1 empty: DP-1,DP-2,DP-3
    bus-ID: 01:00.0 chip-ID: 10de:2504 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
    s-diag: 692mm (27.26")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled
    model: Idek Iiyama PL2792Q serial: <filter> built: 2021 res: mode: 2560x1440
    hz: 60 scale: 100% (1) dpi: 109 gamma: 1.2 chroma: red: x: 0.671 y: 0.333
    green: x: 0.298 y: 0.627 blue: x: 0.141 y: 0.051 white: x: 0.322 y: 0.329
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 2560x1440, 2048x1280, 1920x1200, 1920x1080, 1600x1200, 1680x1050,
    1600x900, 1280x1024, 1440x900, 1280x720, 1024x768, 800x600, 720x576,
    720x480, 640x480
  API: EGL v: 1.5 hw: drv: nvidia nouveau drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: nouveau device: 2 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.144
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    memory: 11.72 GiB
  API: Vulkan v: 1.4.309 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3060 driver: nvidia v: 570.144 device-ID: 10de:2504
    surfaces: xcb,xlib
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1e20 class-ID: 0403
  Device-2: NVIDIA GA106 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:228e
    class-ID: 0403
  API: ALSA v: k6.12.25-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.2 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: NetGear WNDA4100 802.11abgn 3x3:3 [Ralink RT3573]
    driver: rt2800usb type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
    bus-ID: 1-4:4 chip-ID: 0846:9012 class-ID: 0000 serial: <filter>
  IF: wlp0s20u4 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1:2
    chip-ID: 0a12:0001 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
  Device-1: bitlk_mobi_stick maj-min: 254:3 type: Crypto dm: dm-3
    size: 119.01 GiB
  Components:
  p-1: sdd1 maj-min: 8:49 size: 119.01 GiB
  Device-2: bitlk_daniel_stick maj-min: 254:4 type: Crypto dm: dm-4
    size: 30 GiB
  Components:
  p-1: sdd2 maj-min: 8:50 size: 30 GiB
  Device-3: bitlk_bibliothek_stick maj-min: 254:5 type: Crypto dm: dm-5
    size: 30 GiB
  Components:
  p-1: sdd3 maj-min: 8:51 size: 30 GiB
  Device-4: bitlk_wiki_stick maj-min: 254:6 type: Crypto dm: dm-6
    size: 30 GiB
  Components:
  p-1: sdd4 maj-min: 8:52 size: 30 GiB
  Device-5: luks-ac37595d-5b67-408c-82b8-547a678e97e6 maj-min: 254:0
    type: LUKS dm: dm-0 size: 232.59 GiB
  Components:
  p-1: sda2 maj-min: 8:2 size: 232.59 GiB
  Device-6: luks-aa7c5077-2732-494c-8f37-9d6d9852f1d5 maj-min: 254:2
    type: LUKS dm: dm-2 size: 465.76 GiB
  Components:
  p-1: sdb1 maj-min: 8:17 size: 465.76 GiB
  Device-7: luks-97478fb5-267e-493d-8774-49eef2f55050 maj-min: 254:1
    type: LUKS dm: dm-1 size: 465.76 GiB
  Components:
  p-1: sdc1 maj-min: 8:33 size: 465.76 GiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.37 TiB used: 902.37 GiB (64.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD5000AZRX-00A8LB0 size: 465.76 GiB block-size: physical: 4096 B
    logical: 512 B speed: 1.5 Gb/s tech: N/A serial: <filter> fw-rev: 1A01
    scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: Flash Drive FIT
    size: 239.02 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
    fw-rev: 1100 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 232.59 GiB size: 227.88 GiB (97.98%)
    used: 86.01 GiB (37.7%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ac37595d-5b67-408c-82b8-547a678e97e6 label: System
    uuid: 4c2ea2f1-3cfa-4377-8778-97f19f2453fe
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 472 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: NO_LABEL
    uuid: 04E7-F02F
  ID-3: /mnt/org/bibliothek raw-size: 30 GiB size: 30 GiB (100.00%)
    used: 8.45 GiB (28.2%) fs: fuseblk dev: /dev/dm-5 maj-min: 254:5
    mapped: bitlk_bibliothek_stick label: N/A uuid: N/A
  ID-4: /mnt/org/daniel raw-size: 30 GiB size: 30 GiB (100.00%)
    used: 15.51 GiB (51.7%) fs: fuseblk dev: /dev/dm-4 maj-min: 254:4
    mapped: bitlk_daniel_stick label: N/A uuid: N/A
  ID-5: /mnt/org/mobi raw-size: 119.01 GiB size: 119.01 GiB (100.00%)
    used: 34.44 GiB (28.9%) fs: fuseblk dev: /dev/dm-3 maj-min: 254:3
    mapped: bitlk_mobi_stick label: N/A uuid: N/A
  ID-6: /mnt/org/wiki raw-size: 30 GiB size: 30 GiB (100.00%)
    used: 5.66 GiB (18.9%) fs: fuseblk dev: /dev/dm-6 maj-min: 254:6
    mapped: bitlk_wiki_stick label: N/A uuid: N/A
  ID-7: /run/media/schatzi/Data raw-size: 465.76 GiB
    size: 457.38 GiB (98.20%) used: 383.39 GiB (83.8%) fs: ext4 dev: /dev/dm-1
    maj-min: 254:1 mapped: luks-97478fb5-267e-493d-8774-49eef2f55050
    label: Data uuid: aea89950-6192-4055-8c45-0991f2477684
  ID-8: /run/media/schatzi/Extra raw-size: 465.76 GiB
    size: 457.38 GiB (98.20%) used: 368.92 GiB (80.7%) fs: ext4 dev: /dev/dm-2
    maj-min: 254:2 mapped: luks-aa7c5077-2732-494c-8f37-9d6d9852f1d5
    label: Extra uuid: 61a2cc0c-2b1f-46e2-a956-a42b5e447f2a
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Unmounted:
  ID-1: /dev/sdd1 maj-min: 8:49 size: 119.01 GiB fs: bitlocker
    label: 20IAV502790N-0 Mobi 20.06.2023
    uuid: 19a7082b-3c22-4c74-b120-5145a4be6aea
  ID-2: /dev/sdd2 maj-min: 8:50 size: 30 GiB fs: bitlocker
    label: 20IAV502790N-0 Daniel 22.06.2023
    uuid: 31203ad1-da38-4cc3-a989-36c1904f0ce1
  ID-3: /dev/sdd3 maj-min: 8:51 size: 30 GiB fs: bitlocker
    label: 20IAV502790N-0 Bibliothek 20.06.2023
    uuid: 2cf5acb6-cd16-469d-9969-fe23c47bfb15
  ID-4: /dev/sdd4 maj-min: 8:52 size: 30 GiB fs: bitlocker
    label: 20IAV502790N-0 Wiki 20.06.2023
    uuid: 02985be4-7822-4688-af77-2b2f231f9ec5
  ID-5: /dev/sdd5 maj-min: 8:53 size: 30 GiB fs: bitlocker
    label: 20IAV502790N-0 Iav 20.06.2023
    uuid: 40082e01-5629-41e6-9622-4efe2c06129c
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
    type: bluetooth driver: btusb interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 0a12:0001 class-ID: e001
  Hub-2: 1-3:3 info: Realtek 4-Port USB 2.0 Hub ports: 2 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5412
    class-ID: 0900
  Device-1: 1-4:4 info: NetGear WNDA4100 802.11abgn 3x3:3 [Ralink RT3573]
    type: Network driver: rt2800usb interfaces: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 450mA
    chip-ID: 0846:9012 class-ID: 0000 serial: <filter>
  Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 2-3:2 info: Realtek 4-Port USB 3.0 Hub ports: 2 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0412
    class-ID: 0900
  Device-1: 2-3.1:3 info: Silicon Motion - Taiwan (formerly Feiya ) Flash
    Drive type: mass storage driver: usb-storage interfaces: 1 rev: 3.1
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 304mA
    chip-ID: 090c:1000 class-ID: 0806 serial: <filter>
  Hub-5: 3-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-6: 3-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0024
    class-ID: 0900
  Hub-7: 4-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-8: 4-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0024
    class-ID: 0900
  Hub-9: 4-1.5:3 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 214b:7250 class-ID: 0900
  Hub-10: 4-1.5.3:4 info: Monterey BakkerElkhuizen Wired Keyboard S-board
    840 Design USB-Hub ports: 3 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 0566:3020 class-ID: 0900
  Device-1: 4-1.5.3.2:5 info: Logitech Unifying Receiver
    type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Device-2: 4-1.5.3.3:6 info: Monterey BakkerElkhuizen Wired Keyboard
    S-board 840 Design type: keyboard,HID driver: hid-generic,usbhid
    interfaces: 2 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0
    power: 100mA chip-ID: 0566:3013 class-ID: 0300
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A gpu: nvidia temp: 53 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Repos:
  Packages: pm: pacman pkgs: 1804 libs: 444 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.init7.net/manjaro/stable/$repo/$arch
    2: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    3: https://manjaro.kurdy.org/stable/$repo/$arch
    4: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    5: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    6: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    7: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    8: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 326
  1: cpu: 11.9% command: firefox pid: 1724 mem: 486.8 MiB (2.0%)
  2: cpu: 6.8% command: firefox pid: 2169 mem: 248.1 MiB (1.0%)
  3: cpu: 6.8% command: konsole pid: 2813 mem: 181.8 MiB (0.7%)
  4: cpu: 3.9% command: kwin_x11 pid: 987 mem: 194.8 MiB (0.8%)
  5: cpu: 3.0% command: Xorg pid: 815 mem: 121.2 MiB (0.5%)
  Memory top: 5 of 326
  1: mem: 1093.3 MiB (4.5%) command: kjournaldbrowser pid: 1479 cpu: 1.3%
  2: mem: 685.7 MiB (2.8%) command: plasmashell pid: 1008 cpu: 2.5%
  3: mem: 486.8 MiB (2.0%) command: firefox pid: 1724 cpu: 11.9%
  4: mem: 248.1 MiB (1.0%) command: firefox pid: 2169 cpu: 6.8%
  5: mem: 215.1 MiB (0.8%) command: dolphin pid: 2480 cpu: 0.9%
Info:
  Processes: 326 Power: uptime: 16m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 9.33 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.38

This is the journal from the respective session, cintaining errors and critical incidents journalctl --priority=err..crit --no-pager --boot=-1:

Mai 14 09:23:46 schatzi-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20240827/psargs-332)
Mai 14 09:23:46 schatzi-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Mai 14 09:23:46 schatzi-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20240827/psargs-332)
Mai 14 09:23:46 schatzi-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Mai 14 09:23:46 schatzi-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20240827/psargs-332)
Mai 14 09:23:46 schatzi-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Mai 14 09:23:46 schatzi-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20240827/psargs-332)
Mai 14 09:23:46 schatzi-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Mai 14 09:23:46 schatzi-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20240827/psargs-332)
Mai 14 09:23:46 schatzi-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Mai 14 09:23:46 schatzi-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20240827/psargs-332)
Mai 14 09:23:46 schatzi-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Mai 14 09:23:46 schatzi-pc kernel: 
Mai 14 09:23:50 schatzi-pc colord-sane[816]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Mai 14 09:23:52 schatzi-pc systemd[832]: Failed to start Update XDG user dir configuration.
Mai 14 09:24:08 schatzi-pc (trlsd.py)[921]: cameractrlsd.service: Failed at step EXEC spawning /usr/lib/python3.12/site-packages/CameraCtrls/cameractrlsd.py: No such file or directory
Mai 14 09:24:11 schatzi-pc org_kde_powerdevil[1069]: [  1069] busno=2, All features that should not exist detected. Monitor does not indicate unsupported
Mai 14 09:24:17 schatzi-pc bluetoothd[713]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 14 09:24:26 schatzi-pc bluetoothd[713]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 14 09:24:31 schatzi-pc bluetoothd[713]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 14 09:42:48 schatzi-pc bluetoothd[713]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 50:C2:75:18:4E:84: Device or resource busy
Mai 14 09:42:49 schatzi-pc bluetoothd[713]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 50:C2:75:18:4E:84: Device or resource busy
Mai 14 10:00:01 schatzi-pc backintime[4608]: Iav(6) :: ERROR: Unexpected DBusException while initiating dbus.Interface(): org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
Mai 14 10:00:31 schatzi-pc backintime[4608]: Iav(6) :: ERROR: Snapshots directory not accessible. Tries stopped.
Mai 14 10:15:37 schatzi-pc colord-sane[5264]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Mai 14 10:15:38 schatzi-pc colord-sane[5306]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Mai 14 10:15:39 schatzi-pc colord-sane[5320]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Mai 14 10:15:39 schatzi-pc colord-sane[5353]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Mai 14 10:16:18 schatzi-pc systemd[5408]: Failed to start Update XDG user dir configuration.
Mai 14 10:16:33 schatzi-pc bluetoothd[713]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 14 10:16:38 schatzi-pc bluetoothd[713]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down

How I can I track this further?


Mod edit: removed pointless screenshot.

Hi @dano,

Finding errors for specific boot

journalctl --priority=warning..crit --no-pager --boot=-1

Where:

  • The --priority=warning..err argument limits the output to warnings and errors only;
  • the --no-pager formats the output nicely for use here, on the forum; and
  • the --boot=-1 argument limits the output to log messages from the previous boot. This can be adjusted to -2 for the boot before that, -3 to the boot before that, and so on and so forth.

More:

Note that the above text is partially pre-prepared as general instructions. Please take the time to follow the given links and learn more.

Hey @Mirdarthos , sorry for the messy screenshot and thanks for the hints!

Should I post the output above to the original question or below?

Just edit your question and put it there, with explanation. Where the screenshot was is fine.

Ok, done. Posting my warnings, however, breaks the 15k character limit of posts. :grimacing:

So I reduced to errors through critical.

Try this:

journalctl --priority=warning..crit --no-pager --boot=-1 | curl -F 'file=@-' https://0x0.st

And then just provide the link it spits out.

https://0x0.st/8tXq.txt

OK, while I’m no expert, I don’t see anything wrong that seems relevant, except:

xdg-user-dirs-update.service: Failed with result 'exit-code'.

…many of these. While mine is enabled:

$ systemctl --user status xdg-user-dirs-update.service
â—‹ xdg-user-dirs-update.service - Update XDG user dir configuration
Loaded: loaded (/usr/lib/systemd/user/xdg-user-dirs-update.service; enabled; preset: enabled)
Active: inactive (dead) since Mon 2025-05-12 14:46:36 SAST; 1 day 22h ago
Invocation: cb623644ac5f477b9dd248af5babd954
Docs: man:xdg-user-dirs-update(1)
Main PID: 883 (code=exited, status=0/SUCCESS)
Mem peak: 1.7M
CPU: 3ms

May 12 14:46:36 Mirdarthos-PC systemd[868]: Starting Update XDG user dir configuration...
May 12 14:46:36 Mirdarthos-PC systemd[868]: Finished Update XDG user dir configuration.

So I don’t know if it’s significant. But let’s check the logs anyway, since it’s:

  1. having an error when it shouldn’t; and
  2. the timing seem to suspicious to be coincidental.

Please provide the output of:

journalctl --user --priority=warning..crit --no-pager --boot=-1 --unit=xdg-user-dirs-update.service

Where:

  • The --user tells journald this is a user unit and not the default, a system unit;
  • the --priority=warning..err argument limits the output to warnings and errors only;
  • the --no-pager formats the output nicely for use here, on the forum; and
  • the --boot=-1 argument limits the output to log messages from the previous boot. This can be adjusted to -2 for the boot before that, -3 to the boot before that, and so on and so forth.
  • The --unit=xdg-user-dirs-update.service limits the output to be from the specified unit only.

More:

Note that the above text is partially pre-prepared as general instructions. Please take the time to follow the given links and learn more.

Okay:

~ >>> journalctl --user --priority=warning..crit --no-pager --boot=-1 --unit=xdg-user-dirs-update.service                                                                                                                                                  
-- No entries --
~ >>>    
``

:face_with_raised_eyebrow: that…well, that doesn’t look right to me. I honestly don’t know what that does, but I do have it running this side as well:

$ systemctl --user status xdg-user-dirs-update.service
â—‹ xdg-user-dirs-update.service - Update XDG user dir configuration
     Loaded: loaded (/usr/lib/systemd/user/xdg-user-dirs-update.service; enabled; preset: enabled)
     Active: inactive (dead) since Mon 2025-05-12 14:46:36 SAST; 1 day 22h ago
 Invocation: cb623644ac5f477b9dd248af5babd954
       Docs: man:xdg-user-dirs-update(1)
   Main PID: 883 (code=exited, status=0/SUCCESS)
   Mem peak: 1.7M
        CPU: 3ms

May 12 14:46:36 Mirdarthos-PC systemd[868]: Starting Update XDG user dir configuration...
May 12 14:46:36 Mirdarthos-PC systemd[868]: Finished Update XDG user dir configuration.

So…I don’t really know. Please provide the output of:

systemctl --user status xdg-user-dirs-update.service

Hey, thanks a lot! This is the requested output:

~ >>> systemctl --user status xdg-user-dirs-update.service                                                                                                                                                                                                              
â—‹ xdg-user-dirs-update.service - Update XDG user dir configuration
     Loaded: loaded (/usr/lib/systemd/user/xdg-user-dirs-update.service; enabled; preset: enabled)
     Active: inactive (dead) since Wed 2025-05-14 10:18:35 CEST; 3h 18min ago
 Invocation: 799d3de86b304d4db59c3eb595529dae
       Docs: man:xdg-user-dirs-update(1)
   Main PID: 885 (code=exited, status=0/SUCCESS)
   Mem peak: 1.7M
        CPU: 5ms

Mai 14 10:18:35 schatzi-pc systemd[874]: Starting Update XDG user dir configuration...
Mai 14 10:18:35 schatzi-pc systemd[874]: Finished Update XDG user dir configuration.

Should I check in the previous session’s log, if the service has reported anything?

I think so. See if anything pops out, because me? I’m…what’s that word? … Flummoxed and have no idea what to do or where to go from here.

Ok, so thanks for participating my flummoxedness! :grinning:

This is what I get by employing grep on the logs of the problematic session:

 ~ >>> journalctl  --no-pager --boot=-1 | grep xdg-user-dirs-update.service                                                                                                                                                                                              
Mai 14 09:23:52 schatzi-pc systemd[832]: xdg-user-dirs-update.service: Main process exited, code=exited, status=1/FAILURE
Mai 14 09:23:52 schatzi-pc systemd[832]: xdg-user-dirs-update.service: Failed with result 'exit-code'.
Mai 14 10:16:18 schatzi-pc systemd[5408]: xdg-user-dirs-update.service: Main process exited, code=exited, status=1/FAILURE
Mai 14 10:16:18 schatzi-pc systemd[5408]: xdg-user-dirs-update.service: Failed with result 'exit-code'.

And this is the more talkative version:

~ >>> journalctl  --no-pager --boot=-1 | grep xdg                                                                                                                                                                                                                       
Mai 14 09:23:52 schatzi-pc xdg-user-dirs-update[842]: Can't save user-dirs.dirs
Mai 14 09:23:52 schatzi-pc systemd[832]: xdg-user-dirs-update.service: Main process exited, code=exited, status=1/FAILURE
Mai 14 09:23:52 schatzi-pc systemd[832]: xdg-user-dirs-update.service: Failed with result 'exit-code'.
Mai 14 09:24:07 schatzi-pc systemd-xdg-autostart-generator[878]: Configuration file /home/schatzi/.config/autostart/org.kde.yakuake.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Mai 14 09:24:08 schatzi-pc systemd-xdg-autostart-generator[915]: Configuration file /home/schatzi/.config/autostart/org.kde.yakuake.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Mai 14 10:16:18 schatzi-pc xdg-user-dirs-update[5419]: Can't save user-dirs.dirs
Mai 14 10:16:18 schatzi-pc systemd[5408]: xdg-user-dirs-update.service: Main process exited, code=exited, status=1/FAILURE
Mai 14 10:16:18 schatzi-pc systemd[5408]: xdg-user-dirs-update.service: Failed with result 'exit-code'.
Mai 14 10:16:25 schatzi-pc systemd-xdg-autostart-generator[5478]: Configuration file /home/schatzi/.config/autostart/org.kde.yakuake.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
~ >>>            
1 Like

Please provide the output of:

journalctl --user --no-pager --boot=-1 --unit=xdg-user-dirs-update.service                                                                                                                                                  
>>> journalctl --user --no-pager --boot=-1 --unit=xdg-user-dirs-update.service                                                                                                                                                                                        
Mai 14 09:24:07 schatzi-pc systemd[871]: Starting Update XDG user dir configuration...
Mai 14 09:24:07 schatzi-pc systemd[871]: Finished Update XDG user dir configuration.
``

Hmmm OK, the previous session(s):

journalctl --user --no-pager --unit=xdg-user-dirs-update.service

I can’t really and with honesty say it’s been a pleasure, but you are welcome!

This is the tail of the output:

Mai 02 09:02:04 schatzi-pc systemd[900]: Starting Update XDG user dir configuration...
Mai 02 09:02:04 schatzi-pc systemd[900]: Finished Update XDG user dir configuration.
-- Boot fa570c9e330345a998c07908b3e1e589 --
Mai 05 10:56:25 schatzi-pc systemd[893]: Starting Update XDG user dir configuration...
Mai 05 10:56:25 schatzi-pc systemd[893]: Finished Update XDG user dir configuration.
-- Boot 0a13eddfe8a14e44aad49472a1ff5364 --
Mai 05 11:14:03 schatzi-pc systemd[888]: Starting Update XDG user dir configuration...
Mai 05 11:14:03 schatzi-pc systemd[888]: Finished Update XDG user dir configuration.
-- Boot 31c85940862f47568b7d59a2fc9fee36 --
Mai 06 09:18:28 schatzi-pc systemd[926]: Starting Update XDG user dir configuration...
Mai 06 09:18:28 schatzi-pc systemd[926]: Finished Update XDG user dir configuration.
-- Boot b568a6c420414edc803e0447dac7755a --
Mai 07 10:15:10 schatzi-pc systemd[1356]: Starting Update XDG user dir configuration...
Mai 07 10:15:10 schatzi-pc systemd[1356]: Finished Update XDG user dir configuration.
-- Boot e8c64d8c36484167bedd8c11b86447b9 --
Mai 08 12:10:15 schatzi-pc systemd[883]: Starting Update XDG user dir configuration...
Mai 08 12:10:15 schatzi-pc systemd[883]: Finished Update XDG user dir configuration.
-- Boot 0d396d2556124acfae53e7b28f96d83a --
Mai 08 20:34:26 schatzi-pc systemd[848]: Starting Update XDG user dir configuration...
Mai 08 20:34:26 schatzi-pc systemd[848]: Finished Update XDG user dir configuration.
-- Boot a920f2ae05124164a5f1abde847612d6 --
Mai 09 19:26:07 schatzi-pc systemd[862]: Starting Update XDG user dir configuration...
Mai 09 19:26:07 schatzi-pc systemd[862]: Finished Update XDG user dir configuration.
-- Boot a7a5844bcfdb49acb1bae8061b1887ca --
Mai 09 20:23:19 schatzi-pc systemd[854]: Starting Update XDG user dir configuration...
Mai 09 20:23:19 schatzi-pc systemd[854]: Finished Update XDG user dir configuration.
-- Boot b5095ad2cef64a949c66dc94b52bd4ad --
Mai 09 20:40:43 schatzi-pc systemd[868]: Starting Update XDG user dir configuration...
Mai 09 20:40:43 schatzi-pc systemd[868]: Finished Update XDG user dir configuration.
-- Boot 56743aa586194dcc8ee798ea404117b7 --
Mai 10 09:27:38 schatzi-pc systemd[864]: Starting Update XDG user dir configuration...
Mai 10 09:27:38 schatzi-pc systemd[864]: Finished Update XDG user dir configuration.
-- Boot c8b970ebc1cc4e0d95d9b8163ab11cb0 --
Mai 14 09:24:07 schatzi-pc systemd[871]: Starting Update XDG user dir configuration...
Mai 14 09:24:07 schatzi-pc systemd[871]: Finished Update XDG user dir configuration.
-- Boot 24f3bfc96b4b4595890d657c6f9dab55 --
Mai 14 10:18:35 schatzi-pc systemd[874]: Starting Update XDG user dir configuration...
Mai 14 10:18:35 schatzi-pc systemd[874]: Finished Update XDG user dir configuration.
``

It all looks good from what I see, so I’ll have to come sit with you in the Flummoxed corner.

I appreciate the help and the company!

Let’s see, if we can attract more people.

1 Like

Plasma does not automatically log you out, and you then also don’t try “logging back in”.

The Plasma login screen comes from sddm, the display manager. The lock screen comes from kscreenlocker. Those are two very different processes, even though they visually look very similar.

So, what you are having a problem with, is kscreenlocker, and for that matter, you’re not the only one. And the one thing all of the affected people have in common is that they have an Nvidia GPU. :male_detective: