Bug 459568 - Keyboard output is being ignored after waking up when in "Unify outputs" mode.
Summary: Keyboard output is being ignored after waking up when in "Unify outputs" mode.
Status: RESOLVED WORKSFORME
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: 5.25.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-23 15:24 UTC by retired
Modified: 2022-09-23 21:15 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description retired 2022-09-23 15:24:59 UTC 
SUMMARY
Today I stumbled on an interesting bug, I couldn't input my password after resume to ram, lockscreen was staying empty.
I tested in all modes provided by Kscreen OSD and it turns out that I can reliably prevent myself from unlocking session by choosing "Unify outputs". All other options in Super+P menu work fine.


STEPS TO REPRODUCE
1. Switch to "Unify outputs"
2. Put PC to sleep
3. Wake up and try to unlock with password
4. Password field stays empty

OBSERVED RESULT

Password field remains empty, have to switch tty and do what's necessary to reach desktop.

EXPECTED RESULT

Password field should accept keystrokes.

SOFTWARE/OS VERSIONS

Operating System: Arch Linux
KDE Plasma Version: 5.25.90
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.10-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD RENOIR
Nvidia 515.76

Two screens, one at 1080p, another at 1440p. Both @ 144hz.
Comment 1 Nate Graham 2022-09-23 16:38:06 UTC 
1. Is this a regression from Plasma 5.25 or earlier?
2. Does it work in the Wayland session?
Comment 2 retired 2022-09-23 19:10:57 UTC 
I went back to 5.25 and couldn't trigger it either through Wayland or Xorg session.
Now I went back to beta and I can't trigger it on either session as well, that's rather puzzling.

However I did have some resume issues with Wayland, once I was greeted with breeze cursor on black background on both screens. Had to restart session, but I considered it unreliable with Nvidia and am avoiding it.

1. After going back and forth I can't trigger it either on stable not beta.
2. Wayland works, but it has other problems with Nvidia.
Comment 3 Nate Graham 2022-09-23 19:21:04 UTC 
Ok, let's close this bug report for now and re-open it if you manage to find a way to reproduce it, and you can file new bug reports for the other issues you found in the Beta. Thanks a lot!
Comment 4 retired 2022-09-23 21:15:48 UTC 
Sure thing, I will come back if it happens again and it is doing it reliably.