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 606856 - Copying/moving files from one filesystem to another fails if filename contains unallowed characters by the other file system
Copying/moving files from one filesystem to another fails if filename contain...
Status: RESOLVED DUPLICATE of bug 508649
Product: nautilus
Classification: Core
Component: File and Folder Operations
unspecified
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-13 14:46 UTC by Otto Kekäläinen
Modified: 2013-04-24 22:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Otto Kekäläinen 2010-01-13 14:46:13 UTC
Steps to reproduce:
1. Open home folder on Ubuntu (file system ext3 or ext4)
2. Make new file called "Cambridge 08\09 images.zip"
3. Insert a USB key made in Windows (file system vfat or ntfs)
4. Copy file to USB key
=> Nautilus complains:
Error copying
Error making file "Cambridge 08\09 images.zip".
> Show more info
- Invalid filaname

The reason is that the reciving file system (vfat/ntfs) cannot have the character "\" in their file names. 

In a situation like this Nautilus or GnomeVFS should
a) automatically rename the file to something like "Cambridge 08-09 images.zip" and notify the user that the files was renamed to avoid illegal characters

b) give a better error message, like:
Error copying
Error making file "Cambridge 08\09 images.zip".
> Show more info
- The file contains characters, that are invalid on the target file system. Rename the file and try again.
Comment 1 António Fernandes 2013-04-24 22:18:30 UTC
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 508649 ***