Bug 456750 - Screen locker broke from Caps Lock key when i wake up the monitor
Summary: Screen locker broke from Caps Lock key when i wake up the monitor
Status: RESOLVED WORKSFORME
Alias: None
Product: kscreenlocker
Classification: Unmaintained
Component: greeter (other bugs)
Version First Reported In: 5.25.3
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-15 11:05 UTC by Arany Tamás
Modified: 2022-08-18 04:35 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arany Tamás 2022-07-15 11:05:36 UTC
When i lock my screen and my monitor goes sleep, the caps lock key behaves like a kill button after i wake up my monitor and I start typing my password, and shows me the "The screen locker is broken and unlocking is not possible anymore." error

RELEVANT sudo journalctl -f -b output:

Jul 15 12:44:03 fedora plasmashell[1520]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:23: TypeError: Cannot read property 'configuration' of null
Jul 15 12:44:03 fedora kwin_wayland[1390]: QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImpl::sessionState'
Jul 15 12:44:03 fedora plasmashell[1520]: requesting unexisting screen 0
Jul 15 12:44:03 fedora plasmashell[1520]: requesting unexisting screen 0
Jul 15 12:44:03 fedora kded5[1506]: kscreen.kded: Config does not have at least one screen enabled, WILL NOT save this config, this is not what user wants.
Jul 15 12:44:04 fedora plasmashell[1520]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: QML Connections: Detected function "onConfigurationChanged" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.
Jul 15 12:44:04 fedora plasmashell[1520]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: QML Connections: Detected function "onRepaintNeeded" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.
Jul 15 12:44:04 fedora plasmashell[1520]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:67: TypeError: Cannot read property 'wallpaper' of null
Jul 15 12:44:04 fedora plasmashell[1520]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:71: TypeError: Cannot read property 'wallpaper' of null
Jul 15 12:44:04 fedora plasmashell[1520]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 15 12:44:04 fedora kscreenlocker_greet[27418]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 15 12:44:04 fedora kscreenlocker_greet[27418]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool
Jul 15 12:44:04 fedora kscreenlocker_greet[27418]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 15 12:44:04 fedora plasmashell[1520]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:179: TypeError: Cannot read property 'containmentDisplayHints' of null
Jul 15 12:44:04 fedora plasmashell[1520]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:271: TypeError: Cannot read property 'location' of null
Jul 15 12:44:04 fedora plasmashell[1520]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 15 12:44:04 fedora plasmashell[1520]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 15 12:44:04 fedora plasmashell[1520]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 15 12:44:04 fedora plasmashell[1520]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Jul 15 12:44:05 fedora plasmashell[13378]: [2022-07-15 12:44:05.269] [197] (device_info_linux.cc:45): NumberOfDevices
Jul 15 12:44:08 fedora plasmashell[13378]: [2022-07-15 12:44:08.272] [197] (device_info_linux.cc:45): NumberOfDevices
Jul 15 12:44:09 fedora audit[27418]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=27418 comm="kscreenlocker_g" exe="/usr/libexec/kscreenlocker_greet" sig=11 res=1
Jul 15 12:44:09 fedora kernel: kscreenlocker_g[27418]: segfault at 55b1bc98cde0 ip 000055b1bc98cde0 sp 00007ffcd14984a8 error 15
Jul 15 12:44:09 fedora kernel: Code: 00 00 50 ea 7e e0 8b 7f 00 00 30 76 1a bc 8b 7f 00 00 b0 5b 73 bc b1 55 00 00 10 3e 63 bc b1 55 00 00 51 01 00 00 00 00 00 00 <a0> 0f ac e0 8b 7f 00 00 e0 13 95 bc b1 55 00 00 28 11 ac e0 8b 7f
Jul 15 12:44:09 fedora kwin_wayland_wrapper[27550]: interface 'wl_callback' has no event 3
Jul 15 12:44:09 fedora kwin_wayland_wrapper[1390]: not a valid new object id (2), message get_registry(n)
Jul 15 12:44:09 fedora kwin_wayland_wrapper[1390]: error in client communication (pid 1390)
Jul 15 12:44:09 fedora kscreenlocker_greet[27550]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Jul 15 12:44:09 fedora kscreenlocker_greet[27550]: The Wayland connection experienced a fatal error: Bad address
Jul 15 12:44:09 fedora kwin_wayland_wrapper[27553]: wl_display@1: error 1: invalid arguments for wl_display@1.get_registry
Jul 15 12:44:09 fedora kscreenlocker_greet[27553]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Jul 15 12:44:09 fedora kscreenlocker_greet[27553]: The Wayland connection experienced a fatal error: Invalid argument
Jul 15 12:44:09 fedora kscreenlocker_greet[27556]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Jul 15 12:44:09 fedora kscreenlocker_greet[27556]: The Wayland connection broke. Did the Wayland compositor die?

FULL sudo journalctl -f -b output: https://pastebin.com/ZEiDb7mR

STEPS TO REPRODUCE
1. Lock the screen, and wait for the display to sleep as well (only the display, the system dont)
2. Wake up the monitor, type password
3. Press the Caps Lock button when you type the password

OBSERVED RESULT
The kscreenlocker will be crashing instantly when i press the caps lock button, and shows me this:
The screen locker is broken and unlocking is not possible anymore.
In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
log in and execute the command:
loginctl unlock...

EXPECTED RESULT
Nothing, just enabling caps lock as intended 

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.3
Kernel Version: 5.18.11-200.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 31.1 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: H310M M.2 2.0
ADDITIONAL INFORMATION
Also i'm using Hungary keyboard if matters.
Comment 1 Nate Graham 2022-07-15 20:22:00 UTC
Well that's weird. Did the kscreenlocker_greet process crash? Can you see if `coredumpctl list kscreenlocker_greet` shows any crashes?
Comment 2 Arany Tamás 2022-07-16 12:09:57 UTC
The output for `coredumpctl list kscreenlocker_greet`: No coredumps found. Also i can able to reproduce this bug with Arch Linux, on the same machine, so not a fedora specific issue.
Comment 3 Nate Graham 2022-07-19 15:02:21 UTC
Thanks, so the screen locker didn't crash. But it says:

> Jul 15 12:44:09 fedora kscreenlocker_greet[27556]: The Wayland connection broke. Did the Wayland compositor die?

So maybe kwin_wayland crashed? What does `coredumpctl list kwin_wayland` say?
Comment 4 Bug Janitor Service 2022-08-03 04:35:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-08-18 04:35:39 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!