[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 [email protected] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #16 from [email protected] --- (In reply to Nate Graham from comment #13) > Thanks. If the current issue is fixed, let's close the bug report. > > I can sympathize with the buggy experience you're having. However it's > important to distinguish between the *lock* screen (KScreenLocker) and the > *login* screen (SDDM). These are actually provide by separate components, > and will have different bugs. > > Your issues sound somewhat graphics-related. Are you by any chance using an > NVIDIA GPU? Thank you for bearing with me, and I apologize for dropping the ball on this. My system is a laptop with an integrated Intel GPU as well as an NVIDIA GPU, but I'm pretty sure that it generally uses the iGPU unless an application specifically asks to run on the dGPU. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #15 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 --- Comment #14 from Bug Janitor Service --- 🐛🧹 ⚠️ 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 Nate Graham changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #13 from Nate Graham --- Thanks. If the current issue is fixed, let's close the bug report. I can sympathize with the buggy experience you're having. However it's important to distinguish between the *lock* screen (KScreenLocker) and the *login* screen (SDDM). These are actually provide by separate components, and will have different bugs. Your issues sound somewhat graphics-related. Are you by any chance using an NVIDIA GPU? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 [email protected] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #12 from [email protected] --- Hi, Currently, I don't think I'm seeing the exact behavior detailed in my original report, but I'm still finding the KDE / SDDM experience to be generally unresponsive and quite frustrating. Frequently, for example, I see the entire login screen, but keypresses don't show - I type the password, but nothing appears on screen and nothing happens for several seconds, at which point the system just unlocks and shows the desktop. I don't know if this is the same issue as the original one or not, but I've just been having so many problems with KDE / SDDM login that I've strongly considered leaving KDE due to them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #11 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 --- Comment #10 from Bug Janitor Service --- 🐛🧹 ⚠️ 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #9 from Nate Graham --- Is it still happening in Plasma 6.3 and also presumably newer versions of other packages in Debian Sid? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 [email protected] changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from [email protected] --- (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) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 --- Comment #7 from Bug Janitor Service --- 🐛🧹 ⚠️ 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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 --- Comment #6 from Nate Graham --- 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) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 --- Comment #5 from [email protected] --- (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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 --- Comment #4 from Nate Graham --- 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? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 --- Comment #3 from [email protected] --- Created attachment 177340 --> https://bugs.kde.org/attachment.cgi?id=177340&action=edit Recording showing lock screen problems -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 Marco Martin changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||[email protected] Resolution|--- |WAITINGFORINFO --- Comment #2 from Marco Martin --- can you provide a video for it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498101] Several second delay before unlock screen appears
https://bugs.kde.org/show_bug.cgi?id=498101 Nate Graham changed: What|Removed |Added CC||[email protected] --- Comment #1 from Nate Graham --- Never seen this before. I suspect there may be a packaging issue at play here, since Debian Sid is still not stable. -- You are receiving this mail because: You are watching all bug changes.
