Copying files from OS X causes errors with icon files

[Joachim Noreiko]

I am copying files from my mac.
I periodically get this error message:

Error "Invalid parameters" while copying "smb://192....s/Icon%0D".

I assume this is because I set a custom icon for a file or folder in OS X, and the problem file is the hidden icon file OS X creates.

[sam tygier (samtygier)]

is this when copying with nautilus?

[Joachim Noreiko (jnoreiko)]

Yes.
I have my OS X share open in Nautilus (via SMB), and I am copying a folder from that to a mounted Windows partition (FAT32).

[Sebastien Bacher (seb128)]

Thanks for your bug. What version of Ubuntu do you use? What filesystem is that? What filename is used for that "Icon%0D"?

[Joachim Noreiko (jnoreiko)]

I am using Ubuntu 5.10.
The filesystem I am trying to copy to is FAT32. The filesystem on the SMB share is OS X's filesystem.

I can confirm that the file that causes the problem is a hidden file on OS X -- trying to copy just this file reproduces the error.
In the OS X terminal, "ls -a" causes it to show as "Icon?". Autocomplete on the OS X terminal produces "Icon^M".
Copying it from the SMB share to my desktop on Ubuntu (ext3 filesystem) works, and produces a (non-hidden) file. This has the same name in the gnome terminal as on OS X, and on the desktop is called "Icon\n" (where \n is a newline character).

[Sebastien Bacher (seb128)]

The issue seems to be to the encoding of the file and vfat not supporting filenames with a such char. That's similar to upstream http://bugzilla.gnome.org/show_bug.cgi?id=163288 by example

[Joachim Noreiko (jnoreiko)]

Should I file this one upstream too?

I think it's a special case: asking the user what to do with each Icon file would be tedious, as there are so many of them on an OS X filesystem. Nautilus should either skip them or translate the filename in some way.

[Sebastien Bacher (seb128)]

you can fix it upstream if you want to, I'm not sure that's a nautilus bug though. OsX is to blame to use some weird name, the fat filesystem is to blame to not support those chars, and nautilus,gnome-vfs are to blame to workaround it

[Chris Wagner (chris-wagner)]

This is basically the same as bug 18562.

[Duncan Lithgow (duncan-lithgow)]

and is now marked as a duplicate of that bug 18562 - further comments there please.