Bug 523956 - When screen turns off after gracelock period while session is locked due to inactivity, it unlocks
Summary: When screen turns off after gracelock period while session is locked due to i...
Status: RESOLVED DUPLICATE of bug 523504
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.7.3
Platform: openSUSE Linux
: VHI grave
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-08-07 03:25 UTC by Andrew Engelbrecht
Modified: 2026-08-19 21:06 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Engelbrecht 2026-08-07 03:25:35 UTC
DESCRIPTION

The screen / login session does not always lock when configured to do so. After the screen turns off, and the 5 seconds of inactivity have long passed, the session sometimes remains unlocked.

I normally check if my laptop is locked by looking whether the screen is off, but with this behavior, I have to check manually.

STEPS TO REPRODUCE
1. Configure System Settings > "Power Management" > "On AC Power" > "Display and Brightness" > "Turn off Screen": 5 minutes
2. Configure System Settings > "Screen locking" > "Lock Screen Automatically": 5 minutes, "Delay before password is required": 5 seconds
3. 

OBSERVED RESULT

Sometimes I walk over to my computer to use it, and when I go to log in, I see that it's already unlocked.

EXPECTED RESULT

The screen should lock when the device is configured to do so.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20260804
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.5-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen AI 5 340 w/ Radeon 840M
Memory: 16 GiB of RAM (14.9 GiB usable)
Graphics Processor: AMD Radeon 840M Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen AI 300 Series)
System Version: A5

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2026-08-12 21:06:29 UTC
This sounds bad.

So it happens when screen turn-off and screen locking are both configured to trigger at the same time?

Does it ever happen when they're set to different times? So, lock screen furn then turn off… or turn off first, then lock?
Comment 2 Andrew Engelbrecht 2026-08-12 21:09:33 UTC
(In reply to Nate Graham from comment #1)
> This sounds bad.
> 
> So it happens when screen turn-off and screen locking are both configured to
> trigger at the same time?

Yes, that's the behavior I've seen so far.

> Does it ever happen when they're set to different times? So, lock screen
> furn then turn off… or turn off first, then lock?

I haven't tested that yet, but I'll give it a try to see if it helps to debug / as a workaround.
Comment 3 Nate Graham 2026-08-12 21:11:49 UTC
Yeah, I'm asking for debugging purposes, not suggesting this as a workaround! Clearly there's a bug somewhere that needs fixing, but we'll need to know how to reproduce it on demand.

Let us know when you've got that info.
Comment 4 Andrew Engelbrecht 2026-08-12 23:41:49 UTC
Okay, so I was able to reproduce the error the first time I set both screen locking and screen power off to 1 minute, with a 5 minute locking delay.

I noticed that there were some updates, so I applied those and rebooted. I then tried locking 1 minute before screen power off,  locking 1 minute after, locking with no screen power off, and with both at the same time again. I haven't been able to reproduce the error after several tests. There was a time that the screen unlocked without me being certain about the time that had elapsed, but that's bad data, so it shouldn't count.

In the past, it would not always happen, but seemed random. I don't know if it's been resolved, but I'll keep testing to see if I can reproduce this behavior.
Comment 5 Andrew Engelbrecht 2026-08-13 00:15:50 UTC
Okay, I tried the 1 minute and 1 minute settings several times, and at first I couldn't reproduce the error. The latest time, the screen turned black, and I counted 8 seconds. I woke the screen up, and saw that it was unlocked.
Comment 6 Andrew Engelbrecht 2026-08-13 01:04:41 UTC
## on battery power:

- 1 minute + 5 seconds screen lock, 2 minute screen dim, 5 minute screen power off, "when locked: immediately"
  - 3/3 times, it did not lock, even when counting to 15 after the screen turned off

- same but never dimming:
  - 1/1 times: didn't lock 15 seconds after the screen went off
  - i also noticed that the screen goes black for a split second, shows graphics again, for a split second, then goes black

- same but never turning off screen:
  - 2/2 also blinks visuals, but screen with a clock shows up with the lockscreen background. screen is locked.

- same but screen turning off after 1 minute (same as lock time), and "when locked: immediately"
  - 3/3 screen was locked after counting to 15

- same, but dim automatically set to "never", and "turn off screen" set to 1 minute
  - 3/3 times the screen was locked after counting to 15

- same, but set screen to lock after 2 minutes, 5 seconds
  - 3/3 times was locked, after > 2 minutes 5 seconds

## on ac power

- 1 minute + 5 seconds screen lock, 2 minute screen dim, 5 minute screen power off, "when locked: immediately"
  - 2/2 times, did not lock after counting to 15 after the screen turned off
  - i also noticed the screen blink before it turned off completely

I stopped testing there. If you want more stats, let me know, and I'll do more.
Comment 7 Andrew Engelbrecht 2026-08-13 01:08:52 UTC
I should note that I also recently saw this issue on another laptop with a 11th Generation Intel Core processor, so it's not specific to AMD hardware.
Comment 8 patchwork_cadet515 2026-08-13 08:47:03 UTC
Hey there. I can also confirm this bug. I'm running CachyOS on a GMKtec NucBox G2 (Intel N100). Clean installed 2 days ago. KDE Plasma Version 6.7.4. Fully up to date.

After some trial and error, I think I've narrowed down to the screen turning off before the "Delay before password required" timer has elapsed. I can reproduce the bug consistently as follows:

Under "Power Management":
    - Set the main "Turn off screen" timer to a high value like 30 minutes (so it doesn't trigger for the purposes of this test)
    - Set the "When locked" timer to 20 seconds

Under "Screen Locking"
    - Set "Lock screen automatically" to 1 minute
    - Set "Delay before password required" to 21 seconds (this is 1 second longer than the "When locked" timer above)

After 1 minute, the lock screen appears, then falls back to the desktop 20 seconds later, the moment the screen turns off.
Comment 9 Nate Graham 2026-08-19 21:06:54 UTC
I can confirm the issue with those steps. After the screen turns off, the session is unlocked!

Looks like this is a duplicate of Bug 523504, which is reporting the same thing.

*** This bug has been marked as a duplicate of bug 523504 ***