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 312150 - Sometimes, asynchronous moves between different file systems are not supported
Sometimes, asynchronous moves between different file systems are not supported
Status: RESOLVED DUPLICATE of bug 309592
Product: gnome-vfs
Classification: Deprecated
Component: File operations
2.11.x
Other All
: Urgent major
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2005-07-31 18:58 UTC by Christian Neumair
Modified: 2005-08-24 22:05 UTC
See Also:
GNOME target: 2.12.x
GNOME version: 2.11/2.12



Description Christian Neumair 2005-07-31 18:58:35 UTC
If GNOME_VFS_XFER_REMOVESOURCE is passed to gnome_vfs_async_xfer, the move
sometimes fails if the source and the target are on different file systems,
since it calls gnome_vfs_move_uri, which checks for check_same_fs_in_uri in
gnome-vfs-cancellable-ops.c:gnome_vfs_move_uri_cancellable.
gnome_vfs_async_xfer should rather copy the files and clean up the source
afterwards if the files are on different FSes.
gnome_vfs_xfer_uri_internal seems to do the right thing if
GNOME_VFS_XFER_USE_UNIQUE_NAMES is TRUE and gnome_vfs_check_same_fs_uris returns
GNOME_VFS_OK which - from what I can see in file-method.c - may not always be
the case. Maybe we have to
a) remove the _USE_UNIQUE_NAMES branch and always do the same_fs voodoo
b) also check for GNOME_VFS_ERROR_INVALID_URI when deciding whether to break in
the same_fs loop.
Comment 1 Luis Villa 2005-08-24 21:43:56 UTC
What's the user-visible impact of this, Manny?
Comment 2 Christian Neumair 2005-08-24 22:03:23 UTC
Sorry, this is actually a duplicate of bug 309592.

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