Bug 506343

Summary:	Unlocking via loginctl over KDE Connect takes 5 seconds since 6.4
Product:	[Plasma] plasmashell	Reporter:	MBR <mbr>
Component:	Screen locking	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	ASSIGNED ---
Severity:	minor	CC:	kdedev, nate, qydwhotmail
Priority:	NOR	Keywords:	regression
Version First Reported In:	6.4.1
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=506567
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description MBR 2025-06-29 13:42:10 UTC

SUMMARY
If I run "Unlock screen" via KDE connect/ssh the lock screen freezes for exactly 5 seconds (the clock stops, seconds freeze) and then the screen unlocks.
If the mouse is moved during those 5 seconds the screen turns black.

STEPS TO REPRODUCE
1. Lock
2. Run "Unlock screen" via KDE connect

OBSERVED RESULT
Lockscreen freezes and unlocks after 5 seconds

EXPECTED RESULT
It should unlock immediately

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250626
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD Radeon RX 6650 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C56
System Version: 2.0

ADDITIONAL INFORMATION
Started with 6.4

Comment 1 TraceyC 2025-10-02 20:01:36 UTC

Thanks for the bug report. I'm sorry we weren't able to respond before now.

I'm not able to reproduce this, attempting to unlock a machine running Plasma built from git-master, using KDE Connect on another machine
I'm also not able to reproduce this when trying to unlock a machine running Plasma 6.4.5

If you're still experiencing this bug, can you attach system logs from the machine that's being unlocked - from just before and until just after the unlock attempt? Thanks.

Comment 2 MBR 2025-10-02 20:32:04 UTC

Hi, the delay is now about ~2 seconds, originally it was exactly 5 (Plasma 6.4.5 now)

Logs when delay occurs:
Oct 02 22:24:49 openSUSE kdeconnectd[2135]: new capabilities for  "Galaxy S24 FE"
Oct 02 22:24:49 openSUSE kdeconnectd[2135]: kdeconnect.plugin.battery: No Primary Battery detected on this system. This may be a bug.
Oct 02 22:24:49 openSUSE kdeconnectd[2135]: kdeconnect.plugin.battery: Total quantity of batteries found:  1
Oct 02 22:24:49 openSUSE kdeconnectd[2135]: kdeconnect.plugin.battery: Primary Battery seems to have been removed. Suspending packets until it is reconnected.
Oct 02 22:24:49 openSUSE kdeconnectd[2135]: kdeconnect.plugin.clipboard: Ignoring clipboard without timestamp
Oct 02 22:24:51 openSUSE kscreenlocker_greet[73530]: pam_kwallet5(kde:auth): pam_kwallet5: Empty or missing password, doing nothing
Oct 02 22:24:51 openSUSE unix_chkpwd[73773]: password check failed for user (user)
Oct 02 22:24:51 openSUSE kscreenlocker_greet[73530]: pam_unix(kde:auth): authentication failure; logname=user uid=1000 euid=1000 tty= ruser= rhost=  user=user
Oct 02 22:24:58 openSUSE systemd[1511]: Started Konsole - Terminal.

How to reproduce:
1. Meta + L
2. Move the mouse so the password input field appears
3. Run unlock via KDE connect
4. Observe frozen screen/black screen if mouse is moved

Important: this does not happen without step #2

Comment 3 Fushan Wen 2025-11-22 08:48:25 UTC

Can reproduce with step 2 included

Comment 4 Bug Janitor Service 2025-11-22 09:50:59 UTC

A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/296