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 670620 - Windows focus changes on the secondary display when switching workspaces
Windows focus changes on the secondary display when switching workspaces
Status: RESOLVED DUPLICATE of bug 645035
Product: mutter
Classification: Core
Component: general
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2012-02-22 15:56 UTC by Jiri Eischmann
Modified: 2012-02-22 17:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jiri Eischmann 2012-02-22 15:56:29 UTC
I'm using this setup:
1. primary display on the right (where I can switch between workspaces)
2. secondary display on the left (always with two windows: maximized IRC chat on the top and Empathy roster behind it), only one workspace

When I switch from one workspace to another on the primary display window focus on the second display changes and Empathy roster window pops up above the maximized IRC chat. It's very annoying.

It seems like a feature because it happens only if windows on the secondary screen have different focus on different workspaces. From user's point of view it's really annoying and confusing because you cannot switch between workspaces on the secondary display, windows don't change/disappear either, but focus changes based on switching between workspaces.

Wanted result: Since there is visually only one workspace on the secondary display and all things behave as if there was one workspace, window focus should stay the same no matter what workspace you have on the primary display.

I'm using GNOME 3.2.1, but the same behavior is in GNOME 3.3 as well.
Comment 1 Florian Müllner 2012-02-22 17:34:04 UTC
Thanks for the bug report. 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 645035 ***