Bug 498101 - Several second delay before unlock screen appears
Summary: Several second delay before unlock screen appears
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (show other bugs)
Version: 6.2.4
Platform: Debian unstable Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-31 21:00 UTC by kde
Modified: 2025-01-30 23:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Recording showing lock screen problems (276.61 KB, video/webm)
2025-01-14 04:15 UTC, kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2024-12-31 21:00:30 UTC
When the screen is locked and a key is pressed or the pointer is moved, initially only the time, date, Debian logo, and background are displayed on the screen, and it takes a while (at least a few seconds, but the time seems to vary) before the full unlock screen (with the password input box, unlock instructions, and sleep and switch user buttons), is displayed. The full unlock screen should appear immediately.

Linux/KDE Plasma: Debian Sid
KDE Plasma Version: 6.24
KDE Frameworks Version: 6.8.0
Qt Version: 6.7.2
Comment 1 Nate Graham 2025-01-04 05:18:05 UTC
Never seen this before. I suspect there may be a packaging issue at play here, since Debian Sid is still not stable.
Comment 2 Marco Martin 2025-01-10 09:51:59 UTC
can you provide a video for it?
Comment 3 kde 2025-01-14 04:15:15 UTC
Created attachment 177340 [details]
Recording showing lock screen problems
Comment 4 Nate Graham 2025-01-14 17:27:24 UTC
Why are there black areas around the screencast? Do you see those on screen as well, or is this an artifact of using OBS to make the recording?
Comment 5 kde 2025-01-14 17:59:08 UTC
(In reply to Nate Graham from comment #4)
> Why are there black areas around the screencast? Do you see those on screen
> as well, or is this an artifact of using OBS to make the recording?

OBS artifact - they're not present on the screen.

This was my first time ever using OBS (in compliance with the KDE bug reporting guidelines), and I had to spend a bit of time trying to figure it out. My screen's resolution is 4K, and OBS offered several preset choices for its "Base (Canvas) Resolution": 1920x1080 was too small and resulted in most of the screen not being included in the recording, so I went with 5121x2880 (? - standard 5K is apparently 5120x2880). I don't know why OBS doesn't provide a 4K preset.
Comment 6 Nate Graham 2025-01-15 18:22:28 UTC
Can you run it in testing mode to see if the same thing happens there?

QT_LOGGING_RULES=kscreenlocker_greet=true /usr/libexec/kscreenlocker_greet --testing

Then paste the output in the terminal window.

(note that the path to kscreenlocker_greet may be different on your system)
Comment 7 Bug Janitor Service 2025-01-30 03:47:29 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 8 kde 2025-01-30 23:17:23 UTC
(In reply to Nate Graham from comment #6)
> Can you run it in testing mode to see if the same thing happens there?
> 
> QT_LOGGING_RULES=kscreenlocker_greet=true /usr/libexec/kscreenlocker_greet
> --testing
> 
> Then paste the output in the terminal window.
> 
> (note that the path to kscreenlocker_greet may be different on your system)

~$ QT_LOGGING_RULES=kscreenlocker_greet=true /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing
kscreenlocker_greet: Greeter is starting up.
kscreenlocker_greet: [PAM worker kde] start: successfully started
kscreenlocker_greet: [PAM worker kde-smartcard] start: successfully started
kscreenlocker_greet: [PAM worker kde-fingerprint] start: successfully started
kscreenlocker_greet: Greeter is running in testing mode
kscreenlocker_greet: Testing mode enabled: true
Locked at 1738278958
kscreenlocker_greet: PamAuthenticators: starting authenticators
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Idle to PamAuthenticators::Authenticating
kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting authentication
kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting authentication
kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard true
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint true
kscreenlocker_greet: [PAM worker kde-fingerprint] Message: Info message: Place your finger on the fingerprint reader
kscreenlocker_greet: PamAuthenticators: Info message from non-interactive authenticator kde-fingerprint
kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: 
kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive authenticator kde
kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await response
kscreenlocker_greet: [PAM worker kde-smartcard] Message: Echo-off prompt: Password: 
kscreenlocker_greet: [PAM worker kde-smartcard] Starting nested event loop to await response
kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Authentication done, result code: 0 (Success)
kscreenlocker_greet: PamAuthenticators: Success from non-interactive authenticator kde-fingerprint
Unlocked
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint false
kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication done, result code: 7 (Authentication failure)
kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, result code: 7 (Authentication failure)