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 692958 - Buggy behavior when using the Hide All Normal Windows/Show Desktop toggle
Buggy behavior when using the Hide All Normal Windows/Show Desktop toggle
Status: RESOLVED DUPLICATE of bug 686928
Product: mutter
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-01-31 18:35 UTC by Georgiy Treyvus
Modified: 2013-01-31 19:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Georgiy Treyvus 2013-01-31 18:35:07 UTC 
This appears to only be a problem with GNOME 3.6.x and not 3.4.x. Anyway what I did was I went into the Keyboard Preferences and rigged the binding Super+D(not that the specic binding matters, the general problem is still the same) to the Hide All Normal Windows/Show Desktop in the Navigation section.

Anyway say I've got two windows open for the sake of discussion call them A and B. Assume A is in focus at the moment. I then press Super+D and of course the desktop is shown as expected. But here's where shit hits the fan. When I press Super+D again directly afterwards(this means without opening windows, closing them, or doing anything else to break the Show Desktop state) and use the toggle the other way window B comes back into focus instead of window A like it always did before.

If I have several windows open then repeatedly invoking the Hide All Normal Windows/Show Desktop action cycles through each of the windows and not in a way anyway near as cool as Alt-Tab or Alt-Backtick.
Comment 1 Florian Müllner 2013-01-31 18:39:03 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 686928 ***
Comment 2 Georgiy Treyvus 2013-01-31 19:02:20 UTC 
Thanks for the fix. You guys are awesome. By next software version do you mean 3.6.whatever the number now is or 3.8.x?
Comment 3 Florian Müllner 2013-01-31 19:07:34 UTC 
3.8 for now, though the fix should be straightforward to port to the 3.6 branch, in case of an additional 3.6 release.