GNOME Bugzilla – Bug 554499
Error on copy when rename the folder destination
Last modified: 2013-04-30 09:58:54 UTC
Please describe the problem: A error is created when the destination folder is renamed before the end of the copie. Steps to reproduce: 1. Copy ( or move ) more than 1 file (big file, for have time to make the 2nd point) 2. Before the copie is finish ( before begin the last file) : rename the destination folder 3. Actual results: Nautilus Eror Box : (sorry it's in french, i can translet if you want but it's easy to understand) Erreur lors de la copie de « Soul Eater 24 vostfr.avi ». Erreur lors de la copie du fichier dans /home/roumano/Desktop/Telecharger/XGngeo-16. More information : Erreur lors de l'ouverture du fichier « /home/roumano/Desktop/Telecharger/XGngeo-16/Soul Eater 24 vostfr.avi » : Aucun fichier ou répertoire de ce type Expected results: Continue the copie Does this happen every time? Yes every time Other information:
I'm not sure this is a bug per se. There is really nothing we can do about it in gvfs (we can't in general catch some other random app renaming the target). However, it could possibly be done in nautilus if both the copy and the rename is done by nautilus. It would be rather complex and risk all sorts of race conditions though. Not sure if this is worth doing.
Yes, excuse me, it's maybe need to be done in nautilus not in gvfs. If a remember correctly, this was working before implementation of gvfs in nautilus.
I cannot even rename the folder while still copying in 3.1.4. Seems like another bug.
I can reproduce on version 3.6 The file being copied at the time of destination renaming completes the copy successfully, but when trying to copy the next file in the batch, this dialog pops up: > . > / \ Error while copying “foo”. > / ! \ > /_____\ There was an error copying the file into %DESTINATION_BEFORE_RENAME. > > [-] Show more details > > Error opening file '%DESTINATION_BEFORE_RENAMING/foo': No such > file or directory > > [ Cancel ] [ Skip All ] [ Skip ]
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 330568 ***