Lockscreen shows when I turn on the computer, and I can enter password and see the desktop, but cannot lock it after that. It just blinks a black screen when I press meta + L or go to Super > Power / Session > Lock.
I’m on Fedora KDE Plasma Desktop 42 and kscreenlock version is 6.3.5-1.
Other users on my distro do not have this problem so it’s related to something else possibly nvidia.
I have Nvidia. One GTX 1070 with manual installation of the driver .run version 575.51.02 and works well when I press Meta + L.
~/Descargas zypper se -iv kscreenlock ✔ 12:24:14
Cargando datos del repositorio...
Leyendo los paquetes instalados...
S | Name | Type | Version | Arch | Repository
---+---------------------+---------+-----------+--------+-----------------------
i+ | kscreenlocker6 | paquete | 6.3.5-1.1 | x86_64 | (Paquetes del sistema)
name: kscreenlocker6
i+ | kscreenlocker6-lang | paquete | 6.3.5-1.1 | noarch | (Paquetes del sistema)
name: kscreenlocker6-lang
i+ | libKScreenLocker6 | paquete | 6.3.5-1.1 | x86_64 | (Paquetes del sistema)
name: libKScreenLocker6
Regards
I dupped 5 minutes ago (before I was with Qt 6.9.0) and lockscreen works yet (with Qt 6.9.1). Gear is updated too to 25.04.2:
~/Descargas kinfo ✔ 17s 13:16:36
Operating System: openSUSE Tumbleweed 20250606
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.1
Kernel Version: 6.14.6-2-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070
Kernel is the 6.14.6 version yet. I can’t build for 6.15 that is now installed, but all goes well with 6.14.6. So, maybe, no Nvidia problem, no Gear problem, no Qt problem.
~/Descargas zypper se -iv kernel-default ✔ 13:18:43
Cargando datos del repositorio...
Leyendo los paquetes instalados...
S | Name | Type | Version | Arch | Repository
---+----------------------+---------+------------+--------+----------------------------
i+ | kernel-default | paquete | 6.15.0-1.1 | x86_64 | Repositorio principal (OSS)
name: kernel-default
i+ | kernel-default | paquete | 6.14.6-2.1 | x86_64 | (Paquetes del sistema)
name: kernel-default
Regards
I have nvidia GeForce RTX 3070
Assuming that other people on the same distro do not have this problem it’s not nvidia related as well.
I will post some logs here and if needed post more relevant logs to resolve this issue.
journalctl -u sddm output:
-- Boot 02b6426835394aed9810c12b0ac5e1c7 --
Jun 09 14:36:13 fedora systemd[1]: Started sddm.service - Simple Desktop Display Manager.
Jun 09 14:36:13 fedora sddm-helper[2048]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Jun 09 14:36:13 fedora sddm-helper[2048]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=985) by (uid=0)
Jun 09 14:36:22 fedora sddm-helper[2190]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Jun 09 14:36:22 fedora sddm-helper[2190]: pam_unix(sddm:auth): user [mirko] has blank password; authenticated without it
Jun 09 14:36:22 fedora sddm-helper[2190]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Jun 09 14:36:22 fedora sddm-helper[2190]: pam_kwallet5(sddm:auth): pam_kwallet5: Couldn't get password (it is empty)
Jun 09 14:36:22 fedora sddm-helper[2190]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Jun 09 14:36:22 fedora sddm-helper[2190]: pam_unix(sddm:session): session opened for user mirko(uid=1000) by mirko(uid=0)
Jun 09 14:36:22 fedora sddm-helper[2190]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Jun 09 14:36:22 fedora sddm-helper[2190]: Starting Wayland user session: "/etc/sddm/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
journalctl -b 0 --no-pager | grep -Ei 'kwin|kscreenlocker|lock|plasma' output:
Jun 09 19:48:24 fedora systemd-resolved[1157]: Clock change detected. Flushing caches.
Jun 09 19:48:25 fedora plasmashell[2646]: org.kde.pulseaudio: No object for name "auto_null"
Jun 09 19:48:25 fedora plasmashell[2646]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Jun 09 19:48:25 fedora plasmashell[2646]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Jun 09 19:48:25 fedora plasmashell[2646]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
Jun 09 19:48:25 fedora plasmashell[2646]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
Jun 09 19:48:28 fedora kscreenlocker_greet[12554]: pam_unix(kde:auth): user [mirko] has blank password; authenticated without it
Jun 09 19:48:28 fedora kscreenlocker_greet[12554]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3003)
Jun 09 19:48:28 fedora kscreenlocker_greet[12554]: Failed to write to the pipe: Bad file descriptor.
Jun 09 19:48:41 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:48:41 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:48:41 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:48:41 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:48:41 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:48:41 fedora kscreenlocker_greet[14813]: qml: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration!
Jun 09 19:48:41 fedora kscreenlocker_greet[14813]: pam_unix(kde:auth): user [mirko] has blank password; authenticated without it
Jun 09 19:48:41 fedora kscreenlocker_greet[14813]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3003)
Jun 09 19:48:41 fedora kscreenlocker_greet[14813]: Failed to write to the pipe: Bad file descriptor.
Jun 09 19:49:05 fedora plasmashell[2646]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jun 09 19:49:05 fedora systemd[2196]: Starting plasma-baloorunner.service - KRunner provider for baloo file indexer...
Jun 09 19:49:05 fedora systemd[2196]: Started plasma-baloorunner.service - KRunner provider for baloo file indexer.
Jun 09 19:49:11 fedora kwin_wayland[2481]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jun 09 19:49:11 fedora plasmashell[2646]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jun 09 19:49:11 fedora kwin_wayland[2481]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jun 09 19:49:41 fedora kwin_wayland[2481]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jun 09 19:53:39 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:53:39 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:53:39 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:53:39 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:53:39 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 09 19:53:39 fedora kscreenlocker_greet[15407]: qml: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration!
Jun 09 19:53:39 fedora kscreenlocker_greet[15407]: pam_unix(kde:auth): user [mirko] has blank password; authenticated without it
Jun 09 19:53:39 fedora kscreenlocker_greet[15407]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3003)
Jun 09 19:53:39 fedora kscreenlocker_greet[15407]: Failed to write to the pipe: Bad file descriptor.
I found the reason for this, it authenticates automatically because my password was blank. It’s silly but can hopefully help someone in the future. Thanks @Krovikan