SUMMARY After updating to Plasma 6.2 Beta, I cannot unlock the laptop with KScreenLocker. It works if I manually lock the screen and unlock directly, or if I manually sleep the laptop and wake it up directly, but not after closing the lid and letting it sleep for a while (e.g., after a whole night). STEPS TO REPRODUCE 1. Close lid 2. Go to sleep 3. Open lid and try to unlock If later I learn how to reliably reproduce the issue in a faster way I will leave a comment. For now, I only experienced this issue for two days in a row after updating to 6.2, but I can't find a way to trigger the issue manually. OBSERVED RESULT KSscreenLock does not work, and I need to change to another TTY and run loginctl unlock-session. EXPECTED RESULT KSscreenLock should always work, like in Plasma 6.1. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.5.0 Qt Version: 6.8.0 Kernel Version: 6.10.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 22 × Intel® Core™ Ultra 7 155H Memory: 30.9 GiB of RAM Graphics Processor: Mesa Intel® Arc Manufacturer: LENOVO Product Name: 21KDS00600 System Version: ThinkPad X1 Carbon Gen 12
When you say "KSscreenLock does not work", does this mean you got the dreaded "screen locker is broken" message? If so, can you do the following: 1. Run journalctl -f 2. Close the lid, wait for it to go to sleep 3. Open the lid, reproducing the problem that the screen locker is broken 4. Unlock manually in another TTY 5. Save the journal log as a file and attach it here Thanks!
Created attachment 173995 [details] journalctl-logs Sorry for the delay. Here are the logs.
Filtering the logs with cat logs.txt | grep kscreenlocker I get these lines: Sep 23 20:03:38 bespin kscreenlocker_greet[97568]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 23 20:03:38 bespin kscreenlocker_greet[97568]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile Sep 23 20:03:43 bespin kscreenlocker_greet[97568]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object TypeError: Type error is not a function Sep 23 20:03:53 bespin kscreenlocker_greet[97568]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object TypeError: Type error is not a function Sep 23 20:04:02 bespin kscreenlocker_greet[97568]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object TypeError: Type error is not a function Sep 23 20:04:06 bespin kernel: kscreenlocker_g[97568]: segfault at 79c30c360608 ip 000079c325db4ec0 sp 00007fffd9e56eb8 error 4 in libQt6Qml.so.6.8.0[1b4ec0,79c325ca7000+3d8000] likely on CPU 6 (core 20, socket 0) Sep 23 20:04:06 bespin kscreenlocker_greet[98239]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. Sep 23 20:04:06 bespin kscreenlocker_greet[98239]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile Sep 23 20:04:08 bespin kscreenlocker_greet[98239]: pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-98239) opened. Sep 23 20:04:38 bespin kscreenlocker_greet[98239]: Failed to write to the pipe: Bad file descriptor. I don't know if it helps...
I discovered one method that seems to work most of the times. Instead of changing to a different TTY, by clicking the arrow (or pressing enter) many times, at some point the screenlocker seems to crash, I get a new instance (although with "worse" graphics, e.g. the profile picture is shown as a square instead of the circle effect. I will try to record a video and put it here as well (probably tomorrow morning).
"qt.qpa.wayland: Creating a fake screen in order for Qt not to crash" seems highly relevant. How many physical screens are connected to this system? Is the laptop plugged into an external monitor?
No external screens, just the laptop built-in screen. Tomorrow I'll be back in the office so I can also check what happens with an external screen.
I tried now with an external screen and in the external one there is not even the field to enter the password. Before, in Plasma 6.1 for example, all screens would behave identically, now there seems to be a difference. I also noticed that I have an extra unknown screen that perhaps is related to this issue somehow. I open Bug 493618 to track that.
> Sep 23 20:04:06 bespin kernel: kscreenlocker_g[97568]: segfault at 79c30c360608 ip 000079c325db4ec0 sp 00007fffd9e56eb8 error 4 in libQt6Qml.so.6.8.0[1b4ec0,79c325ca7000+3d8000] likely on CPU 6 (core 20, socket 0) Can you get a backtrace of the KScreenlocker crash?
I can reproduce the issue on my desktop as well. Operating System: Arch Linux KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.8.0 Kernel Version: 6.11.0-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X3D 12-Core Processor Memory: 93.4 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: ASUS I also got a similar line in the journal: kernel: kscreenlocker_g[417107]: segfault at 10 ip 00007fb97e3afa64 sp 00007ffc928e2d98 error 4 in libQt6Qml.so.6.8.0[1afa64,7fb97e2a7000+3de000] likely on CPU 21 (core 11, socket 0) But it does not appear in the `coredumpctl list`... I have dumps for /usr/bin/kaccess and /usr/lib/kf6/kauth/chargethresholdhelper, but not for kscreenlocker_g
Perhaps I can run gbd /usr/lib/kscreenlocker_greet? I will try...
Okay, that doesn't work because after I close the lid a second kscreenlocker_greet is run by Plasma. That is the one that crashes, after I log in into that one with the trick I mentioned above, then I see the other kscreenlocker_greet that I started manually with gdb. But that one does not crash.
Can you use `coredumpctl` to get a backtrace of the existing crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
There is no crash listed there. What I tried the other day was connecting via ssh and attaching gdb to the running process. But when doing that I never managed to replicate the issue.
Today I experienced yet a different variation of the same (?) issue, which is a high security risk. After opening the laptop lid, kscreenlocker was not shown, only the mouse, but after a few seconds (~10) the desktop was shown without having to enter any password at all.
Maybe it's exiting but not crashing? Can you get the log output of the process before it crashes? I wonder if this could be Bug 493572 or something similar.
I'm sorry I could not provide a useful backtrace for this issue. I had tried several times, but whenever I attack gdb to the running process I don't manage to reproduce the issue. Two notes about this: 1) On my laptop it got way better after Bug 493618 was fixed upstream in the kernel. I still observe the issue sometimes but not every single time. 2) I can also observe the issue sometimes on my desktop, so it is not device specific. I will give report back after updating to the final release. I guess Arch Linux will package 6.2 with Qt 6.7 instead of 6.8 like the Beta release, so perhaps that also helps discard that this is caused by a Qt change.
After a ~week with Plasma 6.2 final with Qt 6.8.0 I never had this issue when running on the laptop alone. That is, never connecting the laptop to an external monitor, to a docking station, etc. The situation is way better than with the Beta because then I could observe the issue also in that situation. However, I still observed some cases when working with an external docking station. The situation that most often triggers the bug is the following: I'm working with the laptop connected to a docking station with lid close and only using the external monitor. I disconnect the laptop from the docking station to go away (laptop goes correctly into sleep). Then, after a while, I open the lid, and I observe the described issue. In some cases, a variation of the issue happens, which I think it's a concerning security issue. A black screen with only the mouse is shown and after waiting for some seconds, the desktop is shown without having to enter any password at all. I will search around to see if there are any other open issues similar to this or in the same direction now that more people are running 6.2. Unfortunately, I still cannot provide any useful backtrace.
This is the best I could get. I connected via ssh to my desktop, attach gdb to the running kscreenlocker_greet process and got the following: (...) Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Downloading source file /usr/src/debug/glibc/glibc/io/../sysdeps/unix/sysv/linux/ppoll.c 0x0000798e60f1abb0 in __GI_ppoll (fds=fds@entry=0x5bbc05d884d0, nfds=nfds@entry=9, timeout=<optimized out>, timeout@entry=0x7ffc9fb512e0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42 42 return SYSCALL_CANCEL (ppoll_time64, fds, nfds, timeout, sigmask, (gdb) continue Continuing. (gdb) set logging enabled on Thread 1 "kscreenlocker_g" received signal SIGSEGV, Segmentation fault. Downloading source file /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4value_p.h 0x0000798e629b01e2 in QV4::Value::isObject (this=0x798e371bf5e8) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4value_p.h:306 306 return b && b->internalClass->vtable->isObject; (gdb) Continuing. Couldn't get registers: No such process. [root@ilum ~]# cat gdb.txt [Thread 0x798e29a006c0 (LWP 4060913) exited] [New process 3628195] Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. Already logging to gdb.txt. As you can see the gdb.txt is not very useful, and the process is not listed in coredumpctl list.
After that Segmentation fault, which happens after trying a few times to introduce the password (without any feedback if it's correct or not), a new kscreenlocker process starts which works as expected to unlock the screen but has somehow "worse" graphics. For example, the profile picture is shown as a square instead of the usual circle. How I can reliable trigger this bug on my desktop is the following: 1. Manually lock the screen with Super + L 2. Turn off the monitor 3. Turn on the monitor 4. Press any key to see kscreenlocker 5. Try to introduce password (kscreenlocker is completely unresponsive) 6. Click on the continue arrow a few times or press Enter a few times until crash 7. If there is no crash, press Esc and repeat steps 4 to 6. Eventually it always crashes.
https://drive.switch.ch/index.php/s/brMKoQJ6QBHS8Hr And here is a video of what I just explained in my previous comment. The cut in ~00:16 was just two or three more attempts, exactly the same as the last that followed. It was just to shorten the video a little bit. But the process was as described above: Esc, password, enter a few times, Esc again. You can also see in the last part of the video what I meant by "bad graphics" version of the lockerscreen. This method triggers the bug 100% of the times. What is not exactly deterministic is how many attempts are needed to crash the process and get the new one that actually works. In the laptop I can also reproduce quite reliably with a docking station but it does not happen 100% of the times. Hope this is useful to debug this annoying bug :)
I see this on Arch as well after updating to 6.2. Seems to reproduce if I put it to sleep when not connected to my external monitor (USB-C with PD), connect it, and then wake it up again. The lock screen appears on my external screen as expected. I type in my password, hit enter, and the interface just freezes. I can still move the cursor. Switching vterms and doing `loginctl unlock-session` unlocks the session successfully. I do *not* see a kscreenlocker segfault in my logs! Operating System: Arch Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.3-arch1-1 (64-bit) Graphics Platform: Wayland
I tried rebuilding kscreenlocker 6.1.5 and installed it. After rebooting my system, I was still able to reproduce the issue, so whatever caused it (in my case) must be coming from some other part of the Plasma 6.2 update. Here are my logs: Oct 17 14:30:00 athena kscreenlocker_greet[1550]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 17 14:30:03 athena kscreenlocker_greet[1550]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object TypeError: Type error is not a function Oct 17 14:30:08 athena kscreenlocker_greet[1550]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object 1.0015118079999998,-0.0004081919999999834,-0.0004081919999999834,0,0,1.00192,0,0,0,0,1.00192,0,0,0,0,1 is not a function Oct 17 14:30:28 athena kscreenlocker_greet[1550]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object 1.0015118079999998,-0.0004081919999999834,-0.0004081919999999834,0,0,1.00192,0,0,0,0,1.00192,0,0,0,0,1 is not a function That `startAuthenticating` failure seems pretty suspect, both the original reporter of this issue and I both see this in our logs.
Sorry to spam the issue a little, but I just want to add that the code mentioned elsewhere in my logs also seems relevant: LockScreenUi.qml:280: TypeError: Property 'respond' of object 1.0015118079999998,-0.0004081919999999834,-0.0004081919999999834,0,0,1.00192,0,0,0,0,1.00192,0,0,0,0,1 is not a function The actual line of code at 280 is: authenticator.respond(password) Obviously the line printed in the debugging statement does not seem to be an authenticator object. I think probably there's a pointer issue somewhere in the C++ code and in the original reporter's case, this results in a segfault, and in my case, it points to valid memory that is nevertheless not the expected authenticator object.
Are you building with Qt 6.7 or Qt 6.8? Are you using [kde-unstable]. If I filter my logs with sudo journalctl | grep segfault, I have many entries, all caused by kscreenlocker since September 14. That day is when I installed the Plasma 6.2 Beta compiled with Qt 6.8 from [kde-unstable]. Maybe this is a regression caused by Qt 6.8?
(In reply to Iyán Méndez Veiga from comment #24) > Are you building with Qt 6.7 or Qt 6.8? Are you using [kde-unstable]. > > If I filter my logs with sudo journalctl | grep segfault, I have many > entries, all caused by kscreenlocker since September 14. That day is when I > installed the Plasma 6.2 Beta compiled with Qt 6.8 from [kde-unstable]. > > Maybe this is a regression caused by Qt 6.8? I'm not using unstable, but actually it looks like Qt 6.8 is now in extra, so I am on 6.8. I think it's very likely that this is the source of the problem, although I'm surprised there hasn't been a swarm of Arch users reporting it. Maybe it's hardware specific somehow.
I am experiencing this unlock failure as well and seeing similar logs on my Arch box with KDE Plasma 6.2.1, Qt 6.8, Frameworks 6.7. It occurs after a decently long sleep, usually when I let it go to sleep instead of a manual trigger. If it is screen related, I have a LG C2 42" and it will usually turn off before my system initiates sleep. Not sure if that is relevant or not.
It seems like sleep is irrelevant here actually. I just encountered the bug again while I stepped away from my computer. When I came back, my screen was off (LG C2 powered down) but my system was still awake. I turned the LG back on and couldn't log in anymore.
I can add some additional information to this to help possibly narrow down the cause of the issue. My setup is a bit complicated and I have noticed this issue on my Laptop (Machine A) but not my Desktop (Machine B) both running the same OS and software versions. Both Machine A and B are plugged into the same lvl1 Techs KVM that connects to 2 1440p monitors and other devices. As I mentioned I can login fine with my Desktop (Machine B) but the Laptop (Machine A) experiences this issue until I unplug it from the dock. Once unplugged from my laptop Dock I can login no problem. Logs from when I attempted to login this morning Oct 18 08:27:39 titan-laptop teams-for-linux[9663]: 08:27:39.110 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked' Oct 18 08:27:41 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object Friday, October 18, 2024 is not a function Oct 18 08:27:43 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object Friday, October 18, 2024 is not a function Oct 18 08:27:44 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object Friday, October 18, 2024 is not a function Oct 18 08:27:47 titan-laptop systemd[1]: dbus-:1.4-org.kde.powerdevil.backlighthelper@2.service: Deactivated successfully. Oct 18 08:27:49 titan-laptop teams-for-linux[9663]: 08:27:49.112 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked' Oct 18 08:27:49 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object Friday, October 18, 2024 is not a function Oct 18 08:27:52 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object Friday, October 18, 2024 is not a function Oct 18 08:27:54 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object Friday, October 18, 2024 is not a function Oct 18 08:27:55 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object Friday, October 18, 2024 is not a function Oct 18 08:27:59 titan-laptop teams-for-linux[9663]: 08:27:59.114 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked' Oct 18 08:27:59 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:02 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:03 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:04 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:09 titan-laptop teams-for-linux[9663]: 08:28:09.116 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked' Oct 18 08:28:11 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object ⢀?瘂 Oct 18 08:28:15 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object ⢀?瘂 Oct 18 08:28:16 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object ⢀?瘂 Oct 18 08:28:17 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object ⢀?瘂 Oct 18 08:28:19 titan-laptop teams-for-linux[9663]: 08:28:19.118 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked' Oct 18 08:28:19 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object ⢀?瘂 Oct 18 08:28:21 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object 1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a function Oct 18 08:28:25 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object 1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a function Oct 18 08:28:26 titan-laptop kscreenlocker_greet[70170]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object 1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a function ``` However looking at the journalCTL logs from before the login attempt\ and I am getting some additional errors. I have a error from the Kernel relating to Intel graphics drivers and possibly DRM. Oct 18 08:28:47 titan-laptop kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:100:pipe A] mismatch in infoframes.enable (expected 0x00000000, found 0x00000004) Oct 18 08:28:47 titan-laptop kernel: ------------[ cut here ]------------ Oct 18 08:28:47 titan-laptop kernel: i915 0000:00:02.0: [drm] pipe state doesn't match! Oct 18 08:28:47 titan-laptop kernel: WARNING: CPU: 14 PID: 2609 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:223 intel_modeset_verify_crtc+0x4ae/0x550 [i915] Oct 18 08:28:47 titan-laptop kernel: Modules linked in: vhost_net vhost vhost_iotlb tap tun udp_diag tcp_diag inet_diag cmac nls_utf8 cifs rdma_cm iw_cm ib_cm ib_core nls_ucs2_utils> Oct 18 08:28:47 titan-laptop kernel: snd_hda_codec_generic snd_soc_hda_codec snd_hda_ext_core snd_soc_core iwlmvm ac97_bus snd_pcm_dmaengine snd_compress snd_hda_intel uvcvideo x86> Oct 18 08:28:47 titan-laptop kernel: firmware_attributes_class dell_wmi_descriptor wmi_bmof processor_thermal_wt_req snd mtd typec_ucsi intel_skl_int3472_tps68470 i2c_mux cfg80211 > Oct 18 08:28:47 titan-laptop kernel: rtsx_pci_sdmmc sha512_ssse3 sha256_ssse3 mmc_core drm_buddy sha1_ssse3 intel_gtt aesni_intel serio_raw nvme gf128mul i2c_algo_bit atkbd crypto_> Oct 18 08:28:47 titan-laptop kernel: CPU: 14 UID: 1000 PID: 2609 Comm: kwin_wayland Tainted: G W OE 6.11.3-3-cachyos #1 1400000003000000474e5500e91c5d6a11fba825 Oct 18 08:28:47 titan-laptop kernel: Tainted: [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Oct 18 08:28:47 titan-laptop kernel: Hardware name: Dell Inc. XPS 15 9510/0C6CP1, BIOS 1.31.0 07/12/2024 Oct 18 08:28:47 titan-laptop kernel: RIP: 0010:intel_modeset_verify_crtc+0x4ae/0x550 [i915] Oct 18 08:28:47 titan-laptop kernel: Code: ff ff 48 8b 7b 08 e8 61 21 9b d2 48 8b 4b 08 48 8b 51 50 48 85 d2 75 03 48 8b 11 48 c7 c7 50 a2 ca c1 48 89 c6 e8 d2 48 03 d2 <0f> 0b e9 b> Oct 18 08:28:47 titan-laptop kernel: RSP: 0018:ffffa7780fc27978 EFLAGS: 00010246 Oct 18 08:28:47 titan-laptop kernel: RAX: b128c257e0dc4d00 RBX: ffff898acfb54000 RCX: 0000000000000027 Oct 18 08:28:47 titan-laptop kernel: RDX: 00000000ffffefff RSI: 0000000000000002 RDI: ffff899a0f721a48 Oct 18 08:28:47 titan-laptop kernel: RBP: ffff898acfb64e00 R08: 0000000000000fff R09: ffffffff95a59e90 Oct 18 08:28:47 titan-laptop kernel: R10: 0000000000002ffd R11: 0000000000000004 R12: ffff898e959a6000 Oct 18 08:28:47 titan-laptop kernel: R13: ffff898e959a0000 R14: ffff898e959a6000 R15: ffff898afe359800 Oct 18 08:28:47 titan-laptop kernel: FS: 000073e2f69a0f80(0000) GS:ffff899a0f700000(0000) knlGS:0000000000000000 Oct 18 08:28:47 titan-laptop kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 18 08:28:47 titan-laptop kernel: CR2: 0000736bdc4b31c0 CR3: 0000000152724002 CR4: 0000000000f72ef0 Oct 18 08:28:47 titan-laptop kernel: PKRU: 55555554 Oct 18 08:28:47 titan-laptop kernel: Call Trace: Oct 18 08:28:47 titan-laptop kernel: <TASK> Oct 18 08:28:47 titan-laptop kernel: ? __warn+0xd0/0x1c0 Oct 18 08:28:47 titan-laptop kernel: ? intel_modeset_verify_crtc+0x4ae/0x550 [i915 1400000003000000474e550067e9e103415ab20f] Oct 18 08:28:47 titan-laptop kernel: ? report_bug+0x144/0x1f0 Oct 18 08:28:47 titan-laptop kernel: ? handle_bug+0x42/0x70 Oct 18 08:28:47 titan-laptop kernel: ? exc_invalid_op+0x1a/0x50 Oct 18 08:28:47 titan-laptop kernel: ? asm_exc_invalid_op+0x1a/0x20 Oct 18 08:28:47 titan-laptop kernel: ? intel_modeset_verify_crtc+0x4ae/0x550 [i915 1400000003000000474e550067e9e103415ab20f] Oct 18 08:28:47 titan-laptop kernel: ? intel_modeset_verify_crtc+0x4ae/0x550 [i915 1400000003000000474e550067e9e103415ab20f] Oct 18 08:28:47 titan-laptop kernel: intel_atomic_commit_tail+0xaf2/0x12d0 [i915 1400000003000000474e550067e9e103415ab20f] Oct 18 08:28:47 titan-laptop kernel: ? __flush_workqueue+0x4c9/0x550 Oct 18 08:28:47 titan-laptop kernel: intel_atomic_commit+0x2e7/0x320 [i915 1400000003000000474e550067e9e103415ab20f] Oct 18 08:28:47 titan-laptop kernel: drm_atomic_commit+0xc0/0xf0 Oct 18 08:28:47 titan-laptop kernel: ? __pfx___drm_printfn_info+0x10/0x10 Oct 18 08:28:47 titan-laptop kernel: drm_mode_atomic_ioctl+0x621/0xc50 Oct 18 08:28:47 titan-laptop kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Oct 18 08:28:47 titan-laptop kernel: drm_ioctl_kernel+0xbf/0x100 Oct 18 08:28:47 titan-laptop kernel: drm_ioctl+0x355/0x4d0 Oct 18 08:28:47 titan-laptop kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Oct 18 08:28:47 titan-laptop kernel: ? syscall_exit_to_user_mode+0x97/0xc0 Oct 18 08:28:47 titan-laptop kernel: __x64_sys_ioctl+0x73/0xc0 Oct 18 08:28:47 titan-laptop kernel: do_syscall_64+0x88/0x170 Oct 18 08:28:47 titan-laptop kernel: ? __x64_sys_ioctl+0x97/0xc0 Oct 18 08:28:47 titan-laptop kernel: ? syscall_exit_to_user_mode+0x97/0xc0 Oct 18 08:28:47 titan-laptop kernel: ? do_syscall_64+0x94/0x170 Oct 18 08:28:47 titan-laptop kernel: ? clear_bhb_loop+0x25/0x80 Oct 18 08:28:47 titan-laptop kernel: ? clear_bhb_loop+0x25/0x80 Oct 18 08:28:47 titan-laptop kernel: ? clear_bhb_loop+0x25/0x80 Oct 18 08:28:47 titan-laptop kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e Oct 18 08:28:47 titan-laptop kernel: RIP: 0033:0x73e30732b24f Oct 18 08:28:47 titan-laptop kernel: Code: 00 48 89 44 24 18 31 c0 c7 04 24 10 00 00 00 48 8d 44 24 60 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 0> Oct 18 08:28:47 titan-laptop kernel: RSP: 002b:00007ffcf7301fd0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Oct 18 08:28:47 titan-laptop kernel: RAX: ffffffffffffffda RBX: 00005fff9efa41a0 RCX: 000073e30732b24f Oct 18 08:28:47 titan-laptop kernel: RDX: 00007ffcf73020c0 RSI: 00000000c03864bc RDI: 0000000000000017 Oct 18 08:28:47 titan-laptop kernel: RBP: 00007ffcf73020c0 R08: 000073e2a002c9cc R09: 000073e2a002c9cc Oct 18 08:28:47 titan-laptop kernel: R10: 000073e2a002c770 R11: 0000000000000246 R12: 00000000c03864bc Oct 18 08:28:47 titan-laptop kernel: R13: 0000000000000017 R14: 00005fff991cf020 R15: 000000000000002d Oct 18 08:28:47 titan-laptop kernel: </TASK> Oct 18 08:28:47 titan-laptop kernel: ---[ end trace 0000000000000000 ]--- And additionally Joplin had a core-dump just a moment earlier than this driver issue. It is strange that this issue is happening with KDE but only on my Intel machine with a Dock. Hopefully these details help
A bit of a weird crappy workaround, but if you get into a state where you can't log in, switch to another TTY and kill the kscreenlocker_greeter process. This will cause another kscreenlocker_greeter process to spawn that will allow you to log in. If you're on Nvidia and getting that weird black screen issue when resuming from sleep that you can only get past by switching to another TTY and back, note that the above workaround will cause the exact same bug. On my machine, after I kill kscreenlocker_greeter and switch back to the GUI tty, it will show a black screen. I have to blindly type in my password, switch to another TTY, and then back again to get my display back. Not ideal, but it works better than being forced to reboot every time.
This problem happens to me too, using an external monitor with AMD. I found a trick to make this work: enter a wrong password and then the correct one. I think when the kscreenlocker reload (e.g. wrong passwork, or esc multiple times) the password works, weird. This is my log (the issue is not listed in reverse coredumpctl) kscreenlocker_greet[48169]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object 0.9998906249999999,0,0,0,0,0.9998906249999999,0,0,0,0,0.9998906249999999,0,0.00005468750000003908,0.00005468750000003908,0.00005468750000003908,1 is not a function kscreenlocker_greet[48169]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object 0.9998906249999999,0,0,0,0,0.9998906249999999,0,0,0,0,0.9998906249999999,0,0.00005468750000003908,0.00005468750000003908,0.00005468750000003908,1 is not a function kscreenlocker_greet[48169]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object 0.9998906249999999,0,0,0,0,0.9998906249999999,0,0,0,0,0.9998906249999999,0,0.00005468750000003908,0.00005468750000003908,0.00005468750000003908,1 is not a function org_kde_powerdevil[1162]: Emitting DDCA_Display_Status_Event( 20251.514: DDCA_EVENT_DPMS_ASLEEP, card1-HDMI-A-1, dref: Display_Ref[bus /dev/i2c-1], io_path:/dev/i2c-1] org_kde_powerdevil[1162]: Executed 1 registered callbacks. org_kde_powerdevil[1162]: Emitting DDCA_Display_Status_Event( 20253.516: DDCA_EVENT_DPMS_AWAKE, card1-HDMI-A-1, dref: Display_Ref[bus /dev/i2c-1], io_path:/dev/i2c-1] org_kde_powerdevil[1162]: Executed 1 registered callbacks. kernel: kscreenlocker_g[48169]: segfault at 13 ip 00007b79267b01e6 sp 00007fffabea22a0 error 4 in libQt6Qml.so.6.8.0[7b79266a7000+3de000] likely on CPU 2 (core 2, socket 0) kernel: Code: ec 18 48 8b 02 4c 8b 6e 08 64 48 8b 1c 25 28 00 00 00 48 89 5d d8 48 89 f3 48 85 c8 75 66 48 85 c0 74 61 48 8b 08 48 8b 49 10 <80> 79 0e 00 74 54 49 89 45 00 49 8d 75 08 4c 89 ef 48 8b 03 48 8b kscreenlocker_greet[48389]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. org_kde_powerdevil[1162]: dh=Display_Handle[i2c-1: fd=132], Replacing adjusted sleep multiplier 0.05 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS kscreenlocker_greet[48389]: pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-48389) opened. kscreenlocker_greet[48389]: Failed to write to the pipe: Bad file descriptor.
Changing this to confirmed as a few people can replicate, and they have similar segfault entries in their logs.
Created attachment 175035 [details] attachment-1615672-0.html This may be a duplicate of https://bugs.kde.org/show_bug.cgi?id=483094 On Fri, Oct 18, 2024 at 11:55 PM Iyán Méndez Veiga <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=493145 > > Iyán Méndez Veiga <me@iyanmv.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |CONFIRMED > Ever confirmed|0 |1 > > --- Comment #31 from Iyán Méndez Veiga <me@iyanmv.com> --- > Changing this to confirmed as a few people can replicate, and they have > similar > segfault entries in their logs. > > -- > You are receiving this mail because: > You are on the CC list for the bug.
I've been getting screenlocker issues beginning with 6.2. After screen sleep login goes to second login goes to desktop. If I use Enter, it won't work, have to click on the enter arrow on the dialog. I can avoid all of this by clicking switch user which will take me to a login prompt that will work. OS: ArcoLinux x86_64 Kernel: Linux 6.11.4-arch1-1 Packages: 2184 (pacman) Shell: bash 5.2.37 DE: KDE Plasma 6.2.1 WM: KWin (Wayland) WM Theme: Breeze Theme: Breeze (Light) [Qt], Breeze [GTK2/3] Icons: breeze [Qt], breeze [GTK2/3/4] Font: Noto Sans (10pt, Regular) [Qt], Noto Sans (10pt) [GTK2/3/4] Cursor: breeze (24px) Terminal: konsole 24.8.2 Terminal Font: Noto Sans Mono (10pt) CPU: AMD Ryzen 7 5700G (16) @ 5.29 GHz GPU: AMD Radeon Vega Series / Radeon Vega Mobile Series [Integrated] Here's the journald output, thanks ksystemlog, during one event as I described: 10/19/24 12:14 PM polkit-kde-authentication-agent-1 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM kwalletd6 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM DiscoverNotifier qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM kdeconnectd 2024-10-19T12:14:39 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM kded6 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM flameshot qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_akonotes_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_migration_agent qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM python qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_control qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM kactivitymanagerd qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM yakuake qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM kalendarac qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_contacts_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_ical_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_maildir_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_maildispatcher_agent qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_indexing_agent qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_birthdays_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM konsole qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM xdg-desktop-portal-kde qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM akonadi_newmailnotifier_agent qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM plasmashell kde.plasmashell: requesting unexisting screen available rect -1 10/19/24 12:14 PM plasmashell kde.plasmashell: requesting unexisting screen available rect -1 10/19/24 12:14 PM plasmashell kde.plasmashell: requesting unexisting screen available rect -1 10/19/24 12:14 PM plasmashell kde.plasmashell: requesting unexisting screen available rect -1 10/19/24 12:14 PM org_kde_powerdevil qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM plasmashell file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:370:21: Unable to assign [undefined] to bool 10/19/24 12:14 PM plasmashell file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:238:17: Unable to assign [undefined] to bool 10/19/24 12:14 PM plasmashell qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM plasmashell kf.plasma.quick: Exposed with no visual parent. Window positioning broken. 10/19/24 12:14 PM plasmashell kf.plasma.quick: Exposed with no visual parent. Window positioning broken. 10/19/24 12:14 PM plasmashell kf.plasma.quick: Exposed with no visual parent. Window positioning broken. 10/19/24 12:14 PM plasmashell kf.plasma.quick: Exposed with no visual parent. Window positioning broken. 10/19/24 12:14 PM kscreenlocker_greet qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/19/24 12:14 PM org_kde_powerdevil Delaying 6 seconds to avoid a false disconnect/connect sequence... 10/19/24 12:14 PM kscreenlocker_greet file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object TypeError: Type error is not a function 10/19/24 12:14 PM kscreenlocker_greet file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object 1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a function 10/19/24 12:14 PM org_kde_powerdevil stabilized_connector_names required 1 extra calls to get_sysfs_drm_connector_names() 10/19/24 12:14 PM org_kde_powerdevil Emitting DDCA_Display_Status_Event( 2918.091: DDCA_EVENT_DPMS_AWAKE, card1-DP-1, dref: Display_Ref[bus /dev/i2c-3], io_path:/dev/i2c-3] 10/19/24 12:14 PM org_kde_powerdevil Executed 1 registered callbacks. 10/19/24 12:14 PM kscreenlocker_greet file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object 1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a function 10/19/24 12:14 PM org_kde_powerdevil dh=Display_Handle[i2c-3: fd=134], Keeping adjusted sleep multiplier 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS 10/19/24 12:14 PM kernel kscreenlocker_g[4586]: segfault at 70304414c934 ip 0000703075db74b7 sp 00007ffd1b436af8 error 4 in libQt6Qml.so.6.8.0[1b74b7,703075ca7000+3de000] likely on CPU 11 (core 3, socket 0) 10/19/24 12:14 PM kernel Code: 00 00 00 66 83 7f 08 01 49 89 f8 49 89 d1 49 89 ca 0f 84 84 00 00 00 3b 77 20 73 72 8b 57 24 89 f0 03 47 0c 39 d0 73 53 89 c2 <81> 7c d7 2c 00 00 01 00 74 5a 49 8b 50 10 48 85 d2 0f 84 d2 00 00 10/19/24 12:14 PM kscreenlocker_greet pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-5424) opened. 10/19/24 12:15 PM kscreenlocker_greet Failed to write to the pipe: Bad file descriptor. 10/19/24 12:15 PM kded6 xsettingsd: Reloading configuration 10/19/24 12:15 PM kded6 xsettingsd: Loaded 14 settings from /home/steve/.config/xsettingsd/xsettingsd.conf
(In reply to Xavier Corredor Llano from comment #30) > I found a trick to make this work: enter a wrong password and then the correct one. > I think when the kscreenlocker reload (e.g. wrong passwork, or esc multiple > times) the password works, weird. This workaround doesn't work for me unfortunately. Even if I type the wrong password, nothing happens. It still gets stuck. Only a process kill on the kscreenlocker_greet seems to work for me.
I don't think this issue is a duplicate of 483094. This issue appeared for everyone here when kscreenlocker started to be built on some distros with Qt 6.8, and based on the logs and segfaults seen, there seems to be a specific pointer corruption issue caused by a Qt 6.8 regression. Also, I don't think anyone here has encountered the "stuck" part of 483094. The screen locker functions normally, but attempting to log in results in either a crash (which restarts kscreenlocker and fixes the issue for some users), or a hang.
I updated some packages in my system (mesa, vulkan, and others) and after a reboot, this issue is no longer occurs, kscreenlocker is working fine, at least in my case. It could be related to a problem with the GPU driver and/or Qt6.8...
Cool. I don't suppose that's the case for you as well, Iyán?
Latest updates to Plasma 6.2.2 don't fix the regression for me" 10/23/24 9:15 PM kscreenlocker_greet file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object TypeError: Type error is not a function 10/23/24 9:15 PM kscreenlocker_greet file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object length is not a function 10/23/24 9:15 PM kernel kscreenlocker_g[51816]: segfault at 557e3d0d4140 ip 0000557e3d0d4140 sp 00007fff4cfb3548 error 15 likely on CPU 3 (core 3, socket 0) 10/23/24 9:15 PM kscreenlocker_greet pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-52593) opened.
(In reply to Nate Graham from comment #37) > Cool. I don't suppose that's the case for you as well, Iyán? Nope. Latest version of kernel, mesa and Plasma. Same issue on my side.
I rolled back to kscreenlocker-6.1.4-1, my previous version, as a temporary work around.
Still also experiencing this after updating everything
(In reply to steve from comment #40) > I rolled back to kscreenlocker-6.1.4-1, my previous version, as a temporary > work around. Which seemed to work for a while but then it didn't: 10/25/24 7:39 AM kscreenlocker_greet qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/25/24 7:39 AM kscreenlocker_greet file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object TypeError: Type error is not a function 10/25/24 7:39 AM kernel kscreenlocker_g[25809]: segfault at 1000000010 ip 000073c523641a20 sp 00007ffc4b1d5300 error 4 in libQt6Qml.so.6.8.0[241a20,73c5234a7000+3de000] likely on CPU 8 (core 0, socket 0) 10/25/24 7:39 AM kscreenlocker_greet pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-26419) opened. 10/25/24 7:39 AM kscreenlocker_greet Failed to write to the pipe: Bad file descriptor.
The issue is still occuring for me even with the latest updates today. The problem doesn't occur every time. There are moments where it works okay. For example, it worked for 3 times today until it failed again on the 4th unlock.
This one does appear to match the symptoms of Bug 494927, so marking as a duplicate of that. *** This bug has been marked as a duplicate of bug 494927 ***
(In reply to Nate Graham from comment #44) > This one does appear to match the symptoms of Bug 494927, so marking as a > duplicate of that. > > *** This bug has been marked as a duplicate of bug 494927 *** Agree, will keep an eye there ;)