SUMMARY I believe this bug is new. As the title says when wrong password entered kscreenlocker crashes and systemd basically says go into ctrl+alt+f3, login and then unlock the session with "loginctl unlock-session {session number}" (mine is usually 3). And i noticed i can't bring up virtual keyboard too. So there are multiple issues with the kscreenlocker. STEPS TO REPRODUCE 1. Boot with wayland session 2. Lock the computer 3. Enter wrong password OBSERVED RESULT Kscreenlocker crashes. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240612 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7640HS w/ Radeon 760M Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon 760M Manufacturer: HP Product Name: Victus by HP Gaming Laptop 16-s0xxx System Version: Type1ProductConfigId ADDITIONAL INFORMATION Fixing the virtual keyboard will be a plus.
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks!
(In reply to David Redondo from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. Can you please attach a backtrace of the crash using the > coredumpctl command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? > Thanks! Weirdly this is all i get from coredumpctl > TIME PID UID GID SIG COREFILE EXE SIZE > Sat 2024-06-08 17:33:07 +03 28075 1000 1000 SIGSEGV present /home/monke/.local/share/Steam/compatibilitytools.d/GE-Proton9-7/files/> bin/wine64-preloader 1.1G > Sat 2024-06-08 18:05:07 +03 5700 1000 1000 SIGSEGV present /app/bin/fan-control 3.6M There was no kscreenlocker. So i did journalctl -b priority=3 > Haz 14 16:08:52 monkelaptop kscreenlocker_greet[3184]: pam_pkcs11(kde-smartcard:auth): no valid certificate which meets all requirements found > Haz 14 16:08:56 monkelaptop kscreenlocker_greet[3184]: pam_unix(kde-fingerprint:auth): conversation failed > Haz 14 16:08:56 monkelaptop kscreenlocker_greet[3184]: pam_unix(kde-fingerprint:auth): auth could not identify password for [monke] > Haz 14 16:08:56 monkelaptop kscreenlocker_greet[3184]: pam_unix(kde-smartcard:auth): conversation failed > Haz 14 16:08:56 monkelaptop kscreenlocker_greet[3184]: pam_unix(kde-smartcard:auth): auth could not identify password for [monke] > Haz 14 16:08:59 monkelaptop kscreenlocker_greet[3184]: pam_pkcs11(kde-smartcard:auth): no valid certificate which meets all requirements found > Haz 14 16:08:59 monkelaptop kscreenlocker_greet[3240]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. > Available platform plugins are: xcb, vkkhrdisplay, linuxfb, offscreen, minimal, wayland-egl, vnc, minimalegl, eglfs, wayland. I'm a little bit lost because i don't know if is it just my hardware. I might try another distro from livecd and update this comment.
I do have the same problem on OpenSUSE Tumbleweed 20240613 with fully updated packages. Also running Wayland. I have retrieved some more data from journalctl. The full trace is: <code> Jun 18 08:32:18 mymachine kscreenlocker_greet[3894]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile Jun 18 08:32:19 mymachine kscreenlocker_greet[3894]: pam_kwallet5(kde:auth): pam_kwallet5: pam_sm_authenticate Jun 18 08:32:19 mymachine kscreenlocker_greet[3894]: pam_kwallet5(kde:auth): pam_kwallet5: we were already executed Jun 18 08:32:19 mymachine kscreenlocker_greet[3894]: pam_kwallet5(kde-fingerprint:auth): pam_kwallet5: pam_sm_authenticate Jun 18 08:32:19 mymachine kscreenlocker_greet[3894]: pam_kwallet5(kde-fingerprint:auth): pam_kwallet5: we were already executed Jun 18 08:32:19 mymachine kscreenlocker_greet[3894]: no valid certificate which meets all requirements found Jun 18 08:32:19 mymachine kscreenlocker_greet[3894]: pam_pkcs11(kde-smartcard:auth): no valid certificate which meets all requirements found Jun 18 08:32:19 mymachine kscreenlocker_greet[3894]: pam_kwallet5(kde-smartcard:auth): pam_kwallet5: pam_sm_authenticate Jun 18 08:32:19 mymachine kscreenlocker_greet[3894]: pam_kwallet5(kde-smartcard:auth): pam_kwallet5: we were already executed Jun 18 08:32:20 mymachine unix_chkpwd[3953]: password check failed for user (username) Jun 18 08:32:20 mymachine kscreenlocker_greet[3894]: pam_unix(kde:auth): authentication failure; logname=username uid=1000 euid=1000 tty= ruser= rhost= user=username Jun 18 08:32:20 mymachine kscreenlocker_greet[3894]: pam_unix(kde-smartcard:auth): unexpected response from failed conversation function Jun 18 08:32:20 mymachine kscreenlocker_greet[3894]: pam_unix(kde-smartcard:auth): conversation failed Jun 18 08:32:20 mymachine kscreenlocker_greet[3894]: pam_unix(kde-smartcard:auth): auth could not identify password for [username] Jun 18 08:32:20 mymachine kscreenlocker_greet[3894]: pam_unix(kde-fingerprint:auth): unexpected response from failed conversation function Jun 18 08:32:20 mymachine kscreenlocker_greet[3894]: pam_unix(kde-fingerprint:auth): conversation failed Jun 18 08:32:20 mymachine kscreenlocker_greet[3894]: pam_unix(kde-fingerprint:auth): auth could not identify password for [username] Jun 18 08:32:22 mymachine kscreenlocker_greet[3894]: pam_kwallet5(kde:auth): pam_kwallet5: pam_sm_authenticate Jun 18 08:32:22 mymachine kscreenlocker_greet[3894]: pam_kwallet5(kde:auth): pam_kwallet5: we were already executed Jun 18 08:32:22 mymachine kscreenlocker_greet[3894]: no valid certificate which meets all requirements found Jun 18 08:32:22 mymachine kscreenlocker_greet[3894]: pam_pkcs11(kde-smartcard:auth): no valid certificate which meets all requirements found Jun 18 08:32:22 mymachine kwin_wayland_wrapper[3894]: free(): invalid pointer Jun 18 08:32:23 mymachine kwin_wayland_wrapper[2432]: not a valid new object id (2), message get_registry(n) Jun 18 08:32:23 mymachine kwin_wayland_wrapper[2432]: error in client communication (pid 2432) Jun 18 08:32:23 mymachine kwin_wayland_wrapper[4003]: error: received delete_id for unknown id (42) Jun 18 08:32:23 mymachine kwin_wayland_wrapper[4003]: error: received delete_id for unknown id (61) Jun 18 08:32:23 mymachine kwin_wayland_wrapper[4003]: wl_display@1: error 1: invalid arguments for wl_display@1.get_registry Jun 18 08:32:23 mymachine kscreenlocker_greet[4003]: qt.qpa.wayland: Loading shell integration failed. Jun 18 08:32:23 mymachine kscreenlocker_greet[4003]: qt.qpa.wayland: Attempted to load the following shells QList("layer-shell") Jun 18 08:32:23 mymachine kscreenlocker_greet[4003]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. Jun 18 08:32:23 mymachine kscreenlocker_greet[4003]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland. </code>
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I tested in current plasma version which is 6.1.2 and it doesn't crash completely. But it's a little bit glitchy also virtual keyboard still doesn't work.
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.