An application got stuck at the head of the opened applications stack
Affected version
Provide at least the following information:
- ArchLinux
- Latest Gnome 45
- Wayland
- This is a one-time issue and I've got no STR, so I can't test without extension. But I've very few of them and none recently added.
Bug summary
Laptop isn't rebooted very often (if that might have any impact) and have quite some software opened. In the last 24H some nasty bu appeared as such: One of these applications (Gummi, the LaTeX editor, but I believe it could happen to any one of the software opened) got stuck at the head of the opened applications.
This have the following effects:
- When using Alt-Tab, Gummi is always placed at the far left of the list of icons, whenever was the last time it was used. That means Alt-Tab always use it as first iteration item, and then the currently active window/software come second. That means a single alt-tab push… brings us to the very program we're currently using on the foreground..
- This also affect
Alt-[key above Tab]
(Alt-²
in my case, I thinkAlt-`
on a qwerty-us layout), which is supposed to switch between windows of the program we're on. It seems to pick the first element of the stack of active programs, which here means Gummi. That meansAlt-`
always tries to switch between Gummi Windows; there's only one but it'll still change the program and switch to that window.
Steps to reproduce
Unfortunately, no STR. This is the first time I encounter that bug.
I tries to check journalctl
but found nothing obviously related from both Gnome-shell or Mutter which I believe would be one of the culprits, although curiously journalctl -t gnome-shell
isn't showing every messages coming from gnom-shell I can see without -t
, I don't know why.
EDIT: Curiously, the "switch windows directly" (Alt + escape
) and "Switch windows of an app directly" (Alt + F6
) are unaffected.
EDIT2: Curiously enough, the same issue happened with another program on another computer running same distro one hour ago; I closed the program that had the issue and obviously it wasn't there anymore. Still can't figure out what triggered this, though, as it's a program I didn't interact with for a very long time too…