Bug 471799

Summary: escape to turn off screen only works on wayland
Product: [Unmaintained] kscreenlocker Reporter: tsengalb99
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description tsengalb99 2023-06-30 17:23:18 UTC 
SUMMARY
Pressing escape should turn off the screen when on the lock screen. However, this behavior only happens when I am logged in to a wayland session. Pressing escape on the lock screen on a X11 session does nothing.

STEPS TO REPRODUCE
1. Log in to a wayland 5.27 session
2. Lock the screen
3. Press escape. The screen should turn off
4. Do the same with a X11 session (log out of wayland session first). The screen does not turn off.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 12.0, kernel 6.1.0-9-amd64
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Comment 1 Nate Graham 2023-09-14 19:10:47 UTC 
Yes, I'm afraid some things only work on Wayland for technical reasons.
Comment 2 tsengalb99 2023-09-14 19:12:07 UTC 
what is the exact reason why this can't be implemented in X?

On 9/14/23 15:10, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=471799
>
> Nate Graham <nate@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|REPORTED                    |RESOLVED
>           Resolution|---                         |NOT A BUG
>                   CC|                            |nate@kde.org
>
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> Yes, I'm afraid some things only work on Wayland for technical reasons.
>
Comment 3 Nate Graham 2023-09-14 19:16:30 UTC 
I don't know the exact reason, but it's not relevant. X is dead and we are only focusing on Wayland for the future. There won't be resources available to fix this unless they come from the community and don't reduce code maintainability