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 695336 - Can't move desktop icons to other screen in multi-monitor setup
Can't move desktop icons to other screen in multi-monitor setup
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Desktop
3.6.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 688327 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-03-07 01:41 UTC by jjcazau
Modified: 2013-03-25 11:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Dependencies (10.85 KB, text/plain)
2013-03-07 01:41 UTC, jjcazau
Details

Description jjcazau 2013-03-07 01:41:03 UTC
Created attachment 238265 [details]
Dependencies

i) Steps to reproduce

i.a) Attach mutliple monitors to system
i.b) Try to drag and move a desktop icon to another screen

ii) Expected result

It should be possible to place icons at any desired location.

iii) Actual result:

The icon stays on its screen. However it is moved to the far left or right of the first screen, depending on whether the second screen was attached left or right to the first one.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.7.0-6.14-generic 3.7.0
Uname: Linux 3.7.0-6-generic x86_64
ApportVersion: 2.7-0ubuntu2
Architecture: amd64
Date: Sat Dec 15 15:06:31 2012
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1326x768+2644+157'"
InstallationDate: Installed on 2012-09-27 (78 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120905.2)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to raring on 2012-11-24 (21 days ago)
Comment 1 Cosimo Cecchi 2013-03-19 23:33:36 UTC
That behavior was introduced by the fix for bug 420624. Unfortunately it proved to be more problematic than the original reported bug, so I reverted that commit for 3.8 for now.
Comment 2 António Fernandes 2013-03-25 11:37:59 UTC
*** Bug 688327 has been marked as a duplicate of this bug. ***