GNOME Bugzilla – Bug 325346
Writing CD Image Hangs With No Alert On Bad File Names
Last modified: 2006-01-03 20:53:45 UTC
Please describe the problem: Note: This occured in a 2.6.0 version of nautilus - I could not find a way to indicate this, nor did I see anything in Bugzilla that relates. If this has been address, my apologies. Issue: When using CD Creator to burn a CD/DVD, the application hangs if there are files with "bad Unicode" in their title. This would not be a problem, except that no error information is displayed, and hitting "Cancel" simply reports a cdrecord error to the effect that the .iso file could not be read (well, ya... it never was created because the thing hung! ;) ) Diagnosis: An attempt to create an iso separately (using "mkisofs -J -r -o ../myimage.iso ./*") revealed that the mkisofs fails when trying to make an image from a file with "bad Unicode" - such as the funny combined AE character (called an "ash"?) that appears in titles of things that are trying to be gothic. Renaming the offending files and rerunning CD Creator works. It would be helpful to bomb out of CD Creator with the appropriate message(s) passed on from the mkisofs (or equivalent) rather than hang. It would be stellar to find a way to present something useful like "Please rename file 'foo_with_a_funny_character.mp3' - it contains illegal characters". :) Steps to reproduce: 1. Add a file with a character not supported by Joliet extensions to CD Creator 2. Attempt to burn the CD Actual results: The "Writing CD Image" dialog appears, but the 'spinning CD' image stops, and no progress bar appears. Moving another window across the dialog eliminates the image in the dialog's clipping context and the dialog is never redrawn. Clicking "Cancel" apparently aborts the image creation, but still tries to write the image, causing a separate error. Expected results: An error message stating that the file(s) need(s) to be renamed because the name(s) contain invalid characters (a reference to the supported character encoding would be helpful). Naming the offending files by full path would be most helpful. Does this happen every time? Yes. Other information:
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. The hanging part of the bug has been fixed. The showing of the filename is bug 316177. *** This bug has been marked as a duplicate of 149486 ***