Bug 339660 - One key stroke misses on keyboard shortcut with two keyboards
Summary: One key stroke misses on keyboard shortcut with two keyboards
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 4.11.11
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-04 12:14 UTC by Mikiya Okuno
Modified: 2016-07-26 11:56 UTC (History)
1 user (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 Mikiya Okuno 2014-10-04 12:14:21 UTC
I connect an external keyboard on my laptop PC, so it has two keyboards. I sometimes use the integrated keyboard and sometimes use the external keyboard. I switch keyboards without plugging out the external keyboard.

Right after switching the keyboard, one keystroke for keyboard shortcut is missed or delayed, only if the shortcut is combined one such as CTRL+1.

Reproducible: Always

Steps to Reproduce:
1. Make two keyboards connected to your PC.
2. Assing some action to shortcut CTRL+1.
3. Press CTRL+1 from the keyboard which has not been used.

Actual Results:  
The shortcut is missed.

Expected Results:  
The shortcut action is performed immediately.

I assign "Switch to Desktop 1" to CTRL+1.
Comment 1 Thomas Lübking 2014-10-04 19:38:58 UTC
please run "xev -event keyboard | tee key_events.log"
Make sure the xev window has the keyboard focus and try a key combination that is NOT taken by a global shortcut (or make a special window rule to ignore global shortcuts for xev) - eg. Ctrl+9 (?)

-> attach the log

(it's not reproducible here and we need to figure whether this is a problem in X11/evdev or kglobalaccel)
Comment 2 Martin Flöser 2015-01-07 10:46:19 UTC
waiting for info from comment #1
Comment 3 Mikiya Okuno 2016-07-26 11:56:59 UTC
I'm sorry that I missed to respond to this bug. I do not experience the problem any more (on 5.7.2).