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 544787 - dragging files over a disconnected share link in Place side pane leads to a file transfer attempt
dragging files over a disconnected share link in Place side pane leads to a f...
Status: RESOLVED DUPLICATE of bug 536437
Product: nautilus
Classification: Core
Component: Sidebar
2.22.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-26 00:22 UTC by Roman Ovseitsev
Modified: 2008-07-26 01:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Roman Ovseitsev 2008-07-26 00:22:50 UTC 
Please describe the problem:
Dragging (without dropping!) files over a dead (for example when the connection was terminated by the other end) remote windows share link in Places side pane results in a file transfer attempt.
This obviously should't happen for files only dragged over and not dropped.

Steps to reproduce:
1. Enter 'smb://IP/SHARED_FOLDER_PATH' into the nautilus location field.
2. Link to the directory will appear in the 'Places' side pane.
3. Terminate the connection without unmounting (e.g. shut down the machine providing the share)
4. Drag (without dropping!) any file over the share link in Places side pane


Actual results:
Nautilus attempts to copy the file to the share.

Expected results:
Nothing should happen.

Does this happen every time?


Other information:
Comment 1 A. Walton 2008-07-26 01:15:15 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. You may want to check for a software upgrade.


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