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 738075 - Workplaces are on both monitors even though they should be only on primary
Workplaces are on both monitors even though they should be only on primary
Status: RESOLVED DUPLICATE of bug 737178
Product: gnome-shell
Classification: Core
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-10-07 11:30 UTC by Petr Schindler
Modified: 2014-10-07 11:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Petr Schindler 2014-10-07 11:30:38 UTC 
When I open tweak tool the 'Workplaces only on primary display' option is on (by default. But windows which I have on secondary display usually stay only on one workspace. When I toggle the option off and on again it works properly.

This doesn't happen always. It seems to work sometimes for some application. I can see this usually with empathy (that's because I have it always on secondary display).

Version:
gnome-shell-3.14.0-2.fc21.x86_64
Fedora 21
Comment 1 Petr Schindler 2014-10-07 11:36:06 UTC 
This seems to happen only for windows which appear (are started) on secondary display. It doesn't happen when I move windows there from primary display.

When I am in overview I can see all windows on secondary display right on the place when I'm switching workspaces. But when I close overview (by clicking on some window on primary display) all windows suddenly disappear.

When I switch to some affected window the view is moved to worspace where I run it.
Comment 2 Florian Müllner 2014-10-07 11:40:55 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 737178 ***