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 603669 - Dual head/Multiple Monitor support
Dual head/Multiple Monitor support
Status: RESOLVED DUPLICATE of bug 60280
Product: nautilus
Classification: Core
Component: Desktop
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-12-03 02:49 UTC by Justin
Modified: 2010-02-27 12:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Justin 2009-12-03 02:49:21 UTC 
I am sure this has been raised before, but I would really like to see some of these issues sorted.

When using dual head/multiple monitors on my Ubuntu 9.10 system, I am receiving follow (but not limited to) issues:
	Wallpaper is centered across both screens. Seperate wallpapers would be cool, but I would settle for one per monitor.
	Dead-space recognition - Having my mouse move into dead-space and being lost is one thing, but having icons be moved into it is just too hard to deal with.
	Icons in general - Could it be made that when you select "Make this my primary monitor", that all icons are arranged on that monitor, WITHIN the actual screen resolution, as after all, I am selecting a "Primary monitor" for a reason.

If these bugs could get resolved, it would be a great improvement to gnome, and the Linux desktop!

Cheers
Comment 1 Cosimo Cecchi 2010-02-27 12:29:55 UTC 
1) is fixed already (see bug #147808)
2) is bug #60280
3) is various other bugs, such as bug #341307, #321159 or #60280 itself.

Closing as a duplicate of bug #60280, feel free to report any other bug you find.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 60280 ***