GNOME Bugzilla – Bug 745380
Repeated Alt-Tab fails to switch focus
Last modified: 2020-04-17 18:21:07 UTC
SSIA. Running Shell's Wayland session on F22, pressing Alt-Tab repeatedly between gnome-terminal (Wayland native) and Chrome (XWayland), sometimes it will restack the windows but fail to actually switch focus. Moving the pointer (I have FFM enabled) will actually fix the focus. mutter 3.15.90-1 http://static.fooishbar.org/tmp/shell-wayland-alt-tab-fails.mov
Still present in 3.18.0.
And in latter versions as well. As a fun datapoint, with the current setup: eDP-1 (internal panel, primary): Chrome fullscreen DP-1 (external): terminal part-screen If I have my cursor over Chrome, Alt-Tab usually works fine. But sometimes not. If I have my cursor over the terminal, Alt-Tab basically always fails, and focus reverts to the terminal.
This sound like bug 756272 too
It does sound like it, except I'm using an XWayland which forces CLOCK_MONOTONIC after discussing it with Jasper ... still no luck.
I have the same problem with mutter 3.20.2 on Arch linux. I've applied CLOCK_MONOTONIC the patches from bug 756272 to mutter and xwayland but the problem is still there.
This has worked for me for a long time, so assuming it's no longer a problem.
I've just tested this with mutter 3.28.0 on arch linux and it is still present with sloppy focus enabled. If one window is focused with the mouse over it then trying to switch focus to another window with alt-tab results in the focus shifting briefly to the other window and then back to the original window. It happens when trying to switch between native wayland apps as well.
Created attachment 370406 [details] Screencast showing the problem Here's a screencast - I press Alt-Tab twice and you can see the focus flashes across to the terminal and then back to tweak-tool
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 739718 ***