Bug 317136 - [Regression] locker eats first key (multi-monitor)
Summary: [Regression] locker eats first key (multi-monitor)
Status: RESOLVED FIXED
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: locker-qml (other bugs)
Version First Reported In: 4.10.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-21 15:56 UTC by Matthew Woehlke
Modified: 2014-01-24 23:21 UTC (History)
3 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 Matthew Woehlke 2013-03-21 15:56:42 UTC
The old (pre-4.10) screen locker would accept a key both to interrupt the screen saver (and show the password prompt) and also as the first character of the password. This behavior seems to be gone.

Additionally (presumed related), moving the mouse only wakes one screen, such that the first key is not accepted for the password (as expected), but rather wakes the second screen.

Reproducible: Always

Steps to Reproduce:
1. Obtain a 2+ head system
2. Lock the screen
3a. Move the mouse
4a. Press a letter/number key
- or -
3b. Press a letter/number key
Actual Results:  
Keystroke causes both monitors to show unlock dialog, but does not appear in password input.

Expected Results:  
Keystroke appears in password input.
Comment 1 Klaus S. Madsen 2013-04-18 11:15:31 UTC
Hi,

I can confirm this on Kubuntu 12.10 with KDE 4.10.2 from ppa:kubuntu-ppa/backports. Exact same issue, the first keystroke does not appear in the password field in my multi-monitor setup.
Comment 2 Andriy Gapon 2013-05-30 11:56:49 UTC
I can confirm this (mis-)behavior with KDE 4.10.3 on FreeBSD.
For me it appears to be semi-random.  Sometime some key presses are lost and I get a wrong password message, sometimes it is OK.  On a dual-head setup the probability of losing input is much higher, but it also sometimes happens in a single monitor configuration too.
Second attempt is always successful.
Very annoying!
Comment 3 Rolf Eike Beer 2013-06-22 10:41:09 UTC
Dupe of 314685?
Comment 4 Matthew Woehlke 2013-06-24 15:10:21 UTC
Related, at least. Conceptually I would say yes, but this has an additional wrinkle specific to multi-monitor setups that may have additional technical implications. That being the case, I'm going to leave it to someone else's judgement if they should be marked duplicate.

If so, please add a note to bug 314685 about the additional wrinkle in multi-monitor setups.
Comment 5 Matthew Woehlke 2014-01-24 23:21:42 UTC
This seems to be fixed as of KDE 4.11.x (at least in 4.11.5 I'm not seeing the problem any more).