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 372075 - Joliet warning should list files
Joliet warning should list files
Status: RESOLVED OBSOLETE
Product: nautilus-cd-burner
Classification: Deprecated
Component: cd-burner
2.16.x
Other All
: Normal normal
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
Depends on:
Blocks: 382368
 
 
Reported: 2006-11-07 16:20 UTC by thorwil
Modified: 2009-07-29 10:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description thorwil 2006-11-07 16:20:23 UTC 
Please describe the problem:
Trying to burn files including some with filenames conatining characters that are not allowed in joliet and/or too long filenames brings up a warning with the question wether joliet compatibility should be dropped.

Said dialog should list the problematic filenames, so the use doesn't have to search for the manualy (he might not even know what to look for).

After canceling here, a new dialog informs you that the cd/dvd creator just crashed. Even though the main window stays up, so from a user pov that crash dilaog itslef is the only problem.


Steps to reproduce:



Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Germán Poo-Caamaño 2007-06-07 13:58:52 UTC 
I think this issue is partially fixed.

I'm using GNOME 2.18; and when filenames has a name in a wrong enconding, n-c-b opens a window and list them.

Unfortunately, it doesn't say where is located the file.  I tested in directory with more or less 6000 files, and 300 directories.  So, trying to figure out where the file is located is a real pain.
Comment 2 Bastien Nocera 2009-07-29 10:46:02 UTC 
nautilus-cd-burner has been replaced by Brasero in the GNOME 2.26 release. If your bug still applies to Brasero, please feel free to re-open the bug, and reassign it to brasero itself.