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 552544 - Not xinerama - deadspace aware (fell behind smaller projects like xfce4)
Not xinerama - deadspace aware (fell behind smaller projects like xfce4)
Status: RESOLVED DUPLICATE of bug 60280
Product: nautilus
Classification: Core
Component: Desktop
2.22.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-16 20:10 UTC by jimmy the saint
Modified: 2008-09-17 00:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description jimmy the saint 2008-09-16 20:10:50 UTC
Please describe the problem:
Unlike xfce4, Gnome (via Nautilus) is incapable of detecting and respecting dead space created by mismatched dual-screens.  This is a HUGE usability nightmare when attempting to use dual screens that do not match, as icons disappear into the nether regions.  Even Xfce4 is capable of doing that.  A similar bug was reported in 2001, but I feel that the fact that this puts the gnome DE behind a more minor player warrants a bug report of its own.  It seems that the only attention this issue has received is the marking of so many reported bugs as duplicates.  This is a serious issue that deserves attention.

Steps to reproduce:
1. Get two monitors of unequal size
2. put smaller on left
3. Populate desktop with important icons
4. Enable Xinerama or TwinView
5. Watch many of your important icons disappear into the dead space.


Actual results:
icons are drawn in dead space because Nautilus is not capable of detecting where the actual visible area is within the TwinView/Xinerama setup.

Expected results:
Nautilus should identify actual screen real estate just like Xfce4 and restrict icons to those areas.

Does this happen every time?
Yes

Other information:
Please do not simply file this as a duplicate.  The reason there have been so many duplicate reports of this behavior is that it affects so many people and has not been addressed in the SEVEN years since it was first reported.
Comment 1 Cosimo Cecchi 2008-09-17 00:16:46 UTC
Jimmy, thanks for reporting. This bug anyway *is* a duplicate, and there's no reason why we wouldn't want to mark it as such.
I know this is an old and annoying bug, but it's not by filing duplicates that you will see it solved earlier.


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