GNOME Bugzilla – Bug 373083
Files with vfat "illegal" characters copied onto vfat give non-obvious error
Last modified: 2007-05-28 16:40:58 UTC
Please describe the problem: file names including linebreaks are being accepted but then rejected when trying to move the file to a vfat partition Steps to reproduce: 1. open a text file and write the following including the line break: namelineone namelinetwo.txt 2. Create a new file and paste the above text in as the file name. 3. Try to move the file to a vfat partition, first in nautilus then in bash Actual results: in Nautilus: Error "Invalid parameters" while copying "namelineone namelinetwo.txt". In bash it just reports "no such file" as it's not really possible to enter that file name. It can be renamed with $ mv filenamefirst?filenamesecond.txt filenamefirstfilenamesecond.txt Expected results: When I first create the name I expect the line break to be removed without warning. When I try to copy it I expect a dialog saying that the name is invalid - and offering a sensible alternative. Does this happen every time? yes Other information: I could break this into several bugs if the devs would prefer.
I can confirm that copying files with characters that illegal characters in vfat gives the "Invalid Parameters" error. A simpler test case is create an empty file called ":". Copy that to a fat32 partition. This is not nautilus's fault exactly, but we could handle this case better, such as suggest "good" file names. This could be a pain if you are copying 500 files and one has an invalid file name. Changing Status to NEW and changing summary.
I just moved a file called (including the line break): file-name .pdf ... trying to move it to vfat failed. Nautilus failed with the message: ----------------------------------- Error "Invalid parameters" while copying "/home/duncan/...st-file .txt". Would you like to continue? Retry Cancel ----------------------------------- The error message included the line break before ".pdf" I don't know if this means it's been fixed in an update to Nautilus 2.16.1 - but I'm not seeing it now.
Can you try copying a file called ":" to a fat32 partition and see what message you get Duncan? ':' is a also an illegal character on fat32.
Fails to move or prompt for a solution with file named ":" (without the speechmarks). Same error as in comment #2
*** This bug has been marked as a duplicate of 309584 ***