https://bugs.kde.org/show_bug.cgi?id=475142

            Bug ID: 475142
           Summary: Lock screen does not blur background image if it is
                    activated twice in a row
    Classification: Plasma
           Product: ksplash
           Version: 5.27.4
          Platform: Ubuntu
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: plasma-b...@kde.org
          Reporter: elydgol...@gmail.com
  Target Milestone: ---

SUMMARY
***
Pretty much the title. If the screen is locked twice in a row, the background
does not blur when attempting to enter the user password to unlock the screen.
This is hard to replicate without manually locking the screen twice in the
command line, but it occurs when the "Lock screen automatically" option is
enabled in settings both after a fixed time and when the computer goes to
sleep, and the time intervals for automatic sleep and screen locking and the
same.
***

STEPS TO REPRODUCE
1. Open Settings > Workspace Behavior > Screen Locking
2. Turn Automatic Screen Locking on, both for a specific time interval (say 15
minutes) and "after waking from sleep". Make sure that the computer is set to
automatically go to sleep after the exact same interval of time.
3. Wait for the computer to fall asleep

OBSERVED RESULT
The lock screen does not blur the background when entering a password

EXPECTED RESULT
The lock screen blurs the background when entering a password as normal

ADDITIONAL INFORMATION
This bug can also be replicated with commands. Running `loginctl lock-session`
in a terminal window locks the screen as normal, but running `loginctl
lock-session ; loginctl lock-session` twice in a row causes the buggy
behaviour. Also note that `loginctl lock-session ; sleep 1 ; loginctl
lock-session` locks the screen as normal, but `loginctl lock-session ; sleep
0.01 ; loginctl lock-session`  causes the buggy behaviour, so there must be
some time window in which locking the screen in quick succession causes the
buggy behaviour.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to