GNOME Bugzilla – Bug 316177
"Invalid filename" error doesn't include filename
Last modified: 2006-04-20 07:46:47 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=15321 "When trying to burn a cd with nautilus, I got a told it couldn't due to an invalid filename. It would be good to get told which file was the problem, so the I could rename it."
This error is reported by mkisofs. Unfortunately, it only reports: "Some files have invalid filenames."
*** Bug 322318 has been marked as a duplicate of this bug. ***
Mkisofs sometimes gives useful errors (version 2.01 in Ubuntu); e.g. mkisofs: Error: [name omitted] and [name omitted] have the same Joliet name mkisofs: Joliet tree sort failed. The -joliet-long switch may help you.
http://bugzilla.gnome.org/attachment.cgi?id=55179&action=view is a patch tested on Ubuntu 5.10 (mkisofs version 2.01) to mention the offending filename in the dialog, as outputted by mkisofs.
Did anybody have a look at the patch yet?
Ah. Now I understand my confusion. This error message isn't present in upstream cdrtools. It is present in the de-facto "freedrtools" [1] fork: http://cvs.fedora.redhat.com/viewcvs/devel/cdrtools/mkisofs-iconv-14.patch?view=markup And it indeed includes the string/filename: + if(iconv(inls->iconv_d, &inptr, &inleft, &outptr, &outleft) == + (size_t)-1 && errno == EILSEQ) { + fprintf(stderr, "Incorrectly encoded string (%s) " + "encountered.\nPossibly creating an invalid " + "Joliet extension. Aborting.\n", source); + exit(1); + }
I've committed a slightly modified version of your patch to HEAD. The committed version fixed leaking the GString, doesn't use C++ comments, only g_print()'d when in debugging, and followed the style (ie spaces before "("). Please give this a try and let me know if there are any problems. I haven't been able to test this because I can't figure out how to make an invalid filename.
From http://www.portfoliofaq.com/pfaq/FAQ00352.htm "#4. The 'Joliet' standard for Windows CD supporting long filenames has a limit of 64 characters for the total path (folders & filename). If you need deep nesting, use short folder and file names! Also watch for limitations on the depth of folder nesting that can occur with strict observance of ISO9660 (see first bullet in next list)." That page may tell you how to make an invalid filename.
John, I don't think this bug covers that kind of invalid filename. This covers errors from iconv encoding.
I was the OP, but I'm not sure how I managed to produce an invalid file name. I haven't managed to see the error since.