After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772617 - Delay in showing applications in Alt-Tab switcher
Delay in showing applications in Alt-Tab switcher
Status: RESOLVED DUPLICATE of bug 768531
Product: gnome-shell
Classification: Core
Component: app-switcher
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2016-10-08 16:56 UTC by gareth
Modified: 2016-10-08 17:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description gareth 2016-10-08 16:56:03 UTC 
There is a noticeable delay between starting an application and the application showing up in the default app-switcher in Gnome 3.22 (this version is not an available option in the Version list - hence the 'unspecified').


To replicate:
With a single application running (e.g. System Settings), start Terminal (and a stopwatch).  Repeatedly press the Alt-Tab key combination and notice that, initially, Terminal is not shown.  After 30 seconds of Alt-Tab, Terminal appears in the app-switcher.  A similar issue can be noticed with the Files file manager, which appears after 15 seconds.  Others vary - Google Chrome appears instantaneously.

Workaround:
A workaround is to change the default app-switcher to (e.g) fmuellner's AlternateTab switcher, which doesn't display this issue.
Comment 1 Florian Müllner 2016-10-08 16:57:40 UTC 
Are you using the wayland session?
Comment 2 gareth 2016-10-08 17:20:25 UTC 
Yes, I'm using Wayland.

I've just tried it in an Xorg session and it works fine there.
Comment 3 Florian Müllner 2016-10-08 17:26:56 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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