GNOME Bugzilla – Bug 647443
2nd screen in multiscreen config doesn't get managed by virtual desktop manager
Last modified: 2014-08-01 09:06:14 UTC
Hi everybody, I don't really know if this is a bug or a feature, but the people at #gnome think this behaviour is not intended, too. Setup is as follows: - Gnome 3 built through jhbuild. - Two physical screens, not mirrored. -> The 2nd screen does not seem to belong to any workspace. With gnome2, I had several "big" virtual workspaces, made up by putting the two phys. screens together to one single big one. The guys at IRC suggest, that it would be nice if we had a separate set of workspaces for the 2nd physical screen. Anyway, thank you very much for this very great and modern desktop environment! Best wishes Nicolai
I'm experiencing same issue on manual xrandr setup, here is my config: turbina% cat bin/praca-xrandr.sh #!/bin/sh xrandr --output LVDS1 --auto xrandr --output VGA1 --auto xrandr --output VGA1 --right-of LVDS1 It would be sweet to manage different screen in different workspace set.
This is intentional; you should be able to change that using the /apps/mutter/general/workspaces_only_on_primary gconf key.
I had thought this was intentional, but I fear this is not desired by most users. I would hope eventually a way to control this will be included. Maybe a way to "lock" both screens and even have individual spaces for both? drago01@gmail.com , I have seen that possible solution but wasn't able to change anything on my Arch install? What should we change it to?
Changing that gconf key doesn't change anything. Initially it had been set to 'false'. I set it to true via myuid@desktop:~$ gconftool-2 -t bool -s /apps/mutter/general/workspaces_only_on_primary true -> No change I reset it with: myuid@desktop:~$ gconftool-2 -u /apps/mutter/general/workspaces_only_on_primary myuid@desktop:~$ gconftool-2 -g /apps/mutter/general/workspaces_only_on_primary false Thus, false seems to be the default here. A 'which gconftool-2' shows that it is coming from my jhbuild install.
Intentional? This is inconsistent. One screen is managed through useful workspaces, second works like os x expose. Default behaviour should be: - treat both screens as single workspace (like gnome did before) and manage them together or - treat both screens as a separate set of workspace, showing second column of workspaces on the right (imo best) or - treat both screens as a place to put workspaces, so user decides which workspace is displayed on which screen (ability to drag workspace to screens, to tricky) Personally I thing second option is the best for casual.
(In reply to comment #5) > Changing that gconf key doesn't change anything. > Initially it had been set to 'false'. I set it to true via > myuid@desktop:~$ gconftool-2 -t bool -s > /apps/mutter/general/workspaces_only_on_primary true > -> No change > > I reset it with: > myuid@desktop:~$ gconftool-2 -u /apps/mutter/general/workspaces_only_on_primary > myuid@desktop:~$ gconftool-2 -g /apps/mutter/general/workspaces_only_on_primary > false > > Thus, false seems to be the default here. Yes, the key defaults to false. It is overridden in gnome-shell (/desktop/gnome/shell/windows/workspaces_only_on_primary) with a different default.
So if i took that correctly if i change /desktop/gnome/shell/windows/workspaces_only_on_primary and /apps/mutter/general/workspaces_only_on_primary I should have workspaces on both? if that is the case that didn't work for me, but I am using nvidia 270.30 I think there have been issues related to this driver.
Guys, I'm sorry I did something silly I didn't log out and back in! Now my multiple monitors work perfectly as I desire. Thanks for the help!
Should modifying "/desktop/gnome/shell/windows/workspaces_only_on_primary" work within the current session. Comment #9 states that Wesley had to logout and back in again, is this desired behaviour?
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 652580 ***