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 688327 - Desktop Icons can only be positioned on primary monitor
Desktop Icons can only be positioned on primary monitor
Status: RESOLVED DUPLICATE of bug 695336
Product: nautilus
Classification: Core
Component: Desktop
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-11-14 16:43 UTC by M8R-trk6q51
Modified: 2013-03-25 11:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description M8R-trk6q51 2012-11-14 16:43:44 UTC 
Using a 2 monitor setup (Nvidia TwinView), I am unable to have desktop items positioned on the second monitor's desktop. This has been possible in previous Gnome versions however in 3.6.x I am free to position desktop icons anywhere on the primary screen, but nowhere on the second screen.

More generally, if I drag a .desktop icon from screen 1 to screen 2, it instantly returns to screen 1 when dropped.
Comment 1 Martin Szulecki 2012-12-07 09:33:11 UTC 
+1

This is a regression caused by:
https://bugzilla.gnome.org/show_bug.cgi?id=420624

Particular commit:
http://git.gnome.org/browse/nautilus/commit/?id=1292610b87be44fcd5a7d5a09738cd7f3287325f

If I understood correctly, people are enforced this rules for their multi-head setups now:
"... in other words, desktop icons layout starts from the primary monitor and expands rightwards/downwards..."

Too bad though that on my desk my primary display is the right one and the left one is my secondary.
Comment 2 António Fernandes 2013-03-25 11:37:59 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, GNOME 3.8.

*** This bug has been marked as a duplicate of bug 695336 ***