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 327984 - Copy / paste in the current directory does not work
Copy / paste in the current directory does not work
Status: RESOLVED FIXED
Product: gnome-vfs
Classification: Deprecated
Component: File operations
2.13.x
Other All
: Urgent major
: 2.14
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-21 14:52 UTC by Victor Osadci (Vic)
Modified: 2006-02-06 13:35 UTC
See Also:
GNOME target: 2.14.x
GNOME version: 2.13/2.14



Description Victor Osadci (Vic) 2006-01-21 14:52:05 UTC
Please describe the problem:
Making a copy of a file in the same directory as the original does not work

Steps to reproduce:
1. Enter the directory
2. Select a file
3. Ctrl+C, Ctrl+V / 'Copy' and 'Paste' from the 'Edit' menu / middle click
drag-and-drop

Actual results:
The file is not being copied

Expected results:
Create a copy of the file

Does this happen every time?
Yes

Other information:
Comment 1 Daniel Holbach 2006-01-25 18:05:08 UTC
Was reported as https://launchpad.net/products/nautilus/+bug/29589 as well.
Comment 2 Martin Wehner 2006-01-25 20:39:13 UTC
Can reproduce. Reassigning as it was introduced by this change in gnome-vfs:
http://cvs.gnome.org/viewcvs/gnome-vfs/libgnomevfs/gnome-vfs-xfer.c?r1=1.132&r2=1.133
Comment 3 Federico Mena Quintero 2006-01-28 00:58:50 UTC
I'm pretty sure this will break the trash as well.

Can someone please test this:

touch ~/foo
touch ~/somedir/foo

drag ~/foo to the trash
drag ~/somedir/foo to the trash <- should work

ls ~/.Trash <- should show "foo" and "foo (copy)" or somesuch
Comment 4 Christian Neumair 2006-01-28 10:18:39 UTC
The reason why I submitted the patch was because without it cancelling a directory overwrite (which is not possible ATM) an error dialog with GNOME_VFS_ERROR_FILE_EXISTS showed up. But it is obvious that for instance copy_items relies on GNOME_VFS_ERROR_FILE_EXISTS being returned in overwrite mode GNOME_VFS_XFER_OVERWRITE_MODE_ABORT.

I'm not totally sure but I think handle_overwrite should return GNOME_VFS_ERROR_FILE_EXISTS in non-interactive mode and GNOME_VFS_ERROR_INTERRUPTED in interactive mode (i.e. GNOME_VFS_XFER_OVERWRITE_MODE_QUERY).

Note that handle_error also returns GNOME_VFS_ERROR_INTERRUPTED on GNOME_VFS_XFER_ERROR_ACTION_ABORT in GNOME_VFS_XFER_ERROR_MODE_QUERY.

Setting milestone since this renders some file operations useless.
Comment 5 Alexander Larsson 2006-02-06 13:35:56 UTC
I'm just reverting the patch for now. We can figure out a better solution later, but a warning dialog is less bad than missing functionallity.