Bug 366603 - First alt-tab press not handled
Summary: First alt-tab press not handled
Status: RESOLVED DUPLICATE of bug 333511
Alias: None
Product: kwin
Classification: Plasma
Component: tabbox (show other bugs)
Version: 5.7.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-10 18:39 UTC by Mark
Modified: 2016-09-14 13:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mark 2016-08-10 18:39:50 UTC 
I've notices this for a while now, i think it's since the shared QQmlEngine. But i was never quite sure if i just mis-pressed alt-tab or if the first one really didn't get handled. Now i sat down and really test this. It's really not being handled.

Reproducible: Always

Steps to Reproduce:
1. Restart your Plasma 5 environment. Just killing and restarting plasmashell does not make this issue visible. Better start with a freshly started environment form the login manager.
2. Open 2 applications
3. Press alt+tab
4. Nothing happens
5. Press alt+tab again
6. now it works :)

Actual Results:  
Pressing alt+tab for the first time after logging in from the loginmanager (and starting 2 apps afterwards) does nothing. Pressing alt+tab for the second time works as expected. Any alt+tab presses afterwards works just fine. 

Expected Results:  
The first alt+tab press should also show the window switcher

I tested this on:
- Intel desktop with nvidia graphics
- intel laptop with intel graphics
- virtualbox environment

All show the very same issue.
Comment 1 Martin Flöser 2016-08-11 05:59:18 UTC 
yep, I also noticed it quite some time ago, but never got to investigate it.
Comment 2 Roman Gilg 2016-09-08 08:53:40 UTC 
Just FYI: This happens to me both on Wayland and X with

Alt+Tab and Alt+Shift+Tab (reverse window switch)

Neon Dev Unstable.
Comment 3 Martin Flöser 2016-09-14 13:46:38 UTC 

*** This bug has been marked as a duplicate of bug 333511 ***