Bug 503931

Summary:	long pause between activity and unlock dialog
Product:	[Plasma] plasmashell	Reporter:	Andriy Gapon <avg>
Component:	Screen locking	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	6.3.4
Target Milestone:	1.0
Platform:	FreeBSD Ports
OS:	FreeBSD
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Andriy Gapon 2025-05-08 14:38:40 UTC

SUMMARY

There is frequently a long delay, about 30 seconds, between the mouse and/or keyboard activity and the unlock dialog appearing.

STEPS TO REPRODUCE
1. lock the screen and walk away for a while, so that monitors are turned off (the system itself is a desktop and does not suspend);
2. return and move the mouse and/or press a keyboard key;
3. monitors wake up and I can see the lock screen background but there is no password/unlock dialog.

OBSERVED RESULT

The unlock dialog appears about 30 seconds later.
The actual delay seems to vary from unlock to unlock.
Sometimes it's zero, especially if I've just locked the screen.

EXPECTED RESULT

The unlock dialog appears immediately.

SOFTWARE/OS VERSIONS

FreeBSD: 14.2
KDE Plasma Version:  6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.3

ADDITIONAL INFORMATION

This is X11 / Xcb based ssetup.

Comment 1 Nate Graham 2025-05-08 15:25:05 UTC

Does it happen in a Wayland session too? Or only on X11?

Comment 2 Andriy Gapon 2025-05-08 15:27:30 UTC

(In reply to Nate Graham from comment #1)
> Does it happen in a Wayland session too? Or only on X11?

This may take a while.
I've never used Wayland before.
Hopefully, Plasma + Wayland + nvidia would work for me.

Comment 3 Andriy Gapon 2025-05-15 06:22:16 UTC

Update.
Cannot test right now because of an nvidia issue specific to FreeBSD: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286313
kwin_wayland aborts after printing:
No provider of glEGLImageTargetTexture2DOES found.  Requires one of:
    GL_OES_EGL_image
(My guess that the message comes from libepoxy).

Comment 4 Bug Janitor Service 2025-05-30 03:48:17 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2025-06-14 03:48:04 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.

Comment 6 Andriy Gapon 2025-08-28 07:43:50 UTC

I am happy to report that after a recent upgrade the issue went away.

I think that it was upgrade of nvidia driver to version 580.76.05 (previous one was 570.181) that helped.
But there were also some KDE related upgrades as well, e.g. Frameworks 6.16.0 to 6.17.0, KDE applications 25.04.3 to 25.08.0.

I guess I could try to bisect, but why bother.