Bug 349702 - Laptop keyboard does not work in "present windows" effect
Summary: Laptop keyboard does not work in "present windows" effect
Status: RESOLVED DUPLICATE of bug 347566
Alias: None
Product: kwin
Classification: Plasma
Component: effects-window-management (other bugs)
Version First Reported In: 5.3.1
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-29 07:15 UTC by Teemu Erkkola
Modified: 2015-06-29 08:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented 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 Teemu Erkkola 2015-06-29 07:15:05 UTC 
I have a dell laptop typically connected to a dock with a USB keyboard. Filtering and navigating "present windows" with keyboard works nicely with the external, but not the laptop keyboard. This is especially annoying since it doesn't work even when I detach the dock.

Reproducible: Always

Steps to Reproduce:
(Probably?)
1. Boot a laptop with a connected external keyboard
2. Start kwin
3. Detach external keyboard
4. Launch "present windows"
5. Attempt to filter/navigate using the laptop keyboard

Actual Results:  
keyboard has no effect on the effect

Expected Results:  
keyboard affects the effect
Comment 1 Teemu Erkkola 2015-06-29 07:32:56 UTC 
Correction: the laptop keyboard works when the dock is connected. It doesn't work in that particular effect when the dock is not connected.
Comment 2 Thomas Lübking 2015-06-29 07:46:46 UTC 
Potentially bug #347566 ?

Does it work whatever the dock connection state is as long as you restart kwin_x11 afterwards?
(And stops working after some re-connection)
Comment 3 Teemu Erkkola 2015-06-29 07:59:27 UTC 
It's probably the same bug. I just tried to reproduce the bug with several sequences, and only those with changes to display configuration (in my typical case going from 3 to 1 monitors) made the bug manifest. Sorry for the duplicate.

*** This bug has been marked as a duplicate of bug 347566 ***
Comment 4 Thomas Lübking 2015-06-29 08:05:38 UTC 
No problem - the bug is certainly hard enough to look through.