https://bugs.kde.org/show_bug.cgi?id=476533
Bug ID: 476533
Summary: [kdesrc-build Plasma 6] Pressing Esc no longer turns
off the screen when locked
Classification: Plasma
Product: kscreenlocker
Version: git-master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: putr...@gmail.com
Target Milestone: ---
SUMMARY
With Plasma 6 set up using kdesrc-build and after getting around bug 476508 I
found that pressing Esc does not turn off the screen when locked, and if the
password field is on screen pressing Esc makes it act like I just pressed
Enter, it says "Unlocking failed", shakes the password field and then hides
said field.
This is different from bug 466344 in that I don't get the issue in the distro
installed Plasma 5.27.9, and in that other bug pressing Esc doesn't attempt to
unlock the system like in my case.
STEPS TO REPRODUCE
1. Install Plasma 6 via kdesrc-build
2. Login
3. Lock the screen
4. Press Esc
OBSERVED RESULT
The screen does not turn off.
EXPECTED RESULT
The screen turns off.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Kernel Version: 6.5.9-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 30.6 GiB of RAM
Graphics Processor: AMD Radeon Graphics
ADDITIONAL INFORMATION
kscreenlocker is at commit 6777145016231427cccb4721de1e469a1512715c when I
compiled it.
Also, when I tried adding some QWarning calls at and around [1] and recompiling
I see that the greeter did recognise that the Esc key was pressed, but it never
gets to the `dpms->switchMode(KScreen::Dpms::Off)` call. I don't think it's an
issue with DPMS not being supported since the the turn off screen keyboard
shortcut works just fine, even when the screen is locked.
[1]:
https://invent.kde.org/plasma/kscreenlocker/-/blob/6777145016231427cccb4721de1e469a1512715c/greeter/greeterapp.cpp#L619
--
You are receiving this mail because:
You are watching all bug changes.
