Bug#594753: (no subject)

Kevin Goodsell kevin-dated-1349546341.d2c83f at omegacrash.net
Sun Jul 8 17:59:00 UTC 2012


I've been investigating this since I discovered that Brasero won't burn
valid data discs for me. I don't believe this is a burning problem at
all, but an image generation problem. Brasero burns existing ISOs with
no problems, but fails to create valid ISOs most of the time. This makes
it easy to test, since there's no need to expend discs.

Furthermore, I think the problem is a race condition, but I haven't been
able to fully understand it. Console output clearly shows that there
is a problem, however:

brasero (libisofs)DEBUG : Skipping excluded file /home/kevin/test/Data 
Disc/Test File 01
brasero (libisofs)DEBUG : Skipping excluded file /home/kevin/test/Data 
Disc/Test File 02
brasero (libisofs)DEBUG : Creating low level ECMA-119 tree...
brasero (libisofs)DEBUG : Matching hardlinks...
brasero (libisofs)DEBUG : Sorting the low level tree...
brasero (libisofs)DEBUG : Mangling names...
brasero (libisofs)DEBUG : Creating low level Joliet tree...
brasero (libisofs)DEBUG : Sorting the Joliet tree...
brasero (libisofs)DEBUG : Mangling Joliet names...
brasero (libisofs)DEBUG : Computing position of dir structure
brasero (libisofs)DEBUG : Computing length of pathlist
brasero (libisofs)DEBUG : Computing position of Joliet dir structure
brasero (libisofs)DEBUG : Computing length of Joliet pathlist
brasero (libisofs)DEBUG : Reader thread being cancelled
brasero (libisofs)DEBUG : Starting image writing...
brasero (libisofs)DEBUG : Write volume descriptors
brasero (libisofs)DEBUG : Write Primary Volume Descriptor
brasero (libisofs)DEBUG : Write SVD for Joliet
brasero (libisofs)DEBUG : Writing ISO Path tables
brasero (libisofs)DEBUG : Writing Joliet Path tables
brasero (libisofs)DEBUG : Writing Files...
brasero (libisofs)DEBUG : Processed 558 of 11158 KB (5 %)
brasero (libisofs)DEBUG : Processed 1116 of 11158 KB (10 %)
brasero (libisofs)DEBUG : Processed 1674 of 11158 KB (15 %)
brasero (libisofs)MISHAP : Image write cancelled
brasero (libisofs)DEBUG : Writer thread joined
brasero (libisofs)DEBUG : Reader thread being cancelled
brasero (libisofs)DEBUG : Writer thread joined

"Skipping excluded file" looks suspicious, but I don't believe it's
actually a problem. I'm not sure why, but Brasero seems to set most
files as excluded in the libisofs image object, then add them
individually. The first real sign of trouble is "Reader thread being
cancelled".

For comparison, a run where it succeeded:

brasero (libisofs)DEBUG : Skipping excluded file /home/kevin/test/Data 
Disc/Test File 01
brasero (libisofs)DEBUG : Skipping excluded file /home/kevin/test/Data 
Disc/Test File 02
brasero (libisofs)DEBUG : Creating low level ECMA-119 tree...
brasero (libisofs)DEBUG : Matching hardlinks...
brasero (libisofs)DEBUG : Sorting the low level tree...
brasero (libisofs)DEBUG : Mangling names...
brasero (libisofs)DEBUG : Creating low level Joliet tree...
brasero (libisofs)DEBUG : Sorting the Joliet tree...
brasero (libisofs)DEBUG : Mangling Joliet names...
brasero (libisofs)DEBUG : Computing position of dir structure
brasero (libisofs)DEBUG : Computing length of pathlist
brasero (libisofs)DEBUG : Computing position of Joliet dir structure
brasero (libisofs)DEBUG : Computing length of Joliet pathlist
brasero (libisofs)DEBUG : Starting image writing...
brasero (libisofs)DEBUG : Write volume descriptors
brasero (libisofs)DEBUG : Write Primary Volume Descriptor
brasero (libisofs)DEBUG : Write SVD for Joliet
brasero (libisofs)DEBUG : Writing ISO Path tables
brasero (libisofs)DEBUG : Writing Joliet Path tables
brasero (libisofs)DEBUG : Writing Files...
brasero (libisofs)DEBUG : Processed 558 of 11158 KB (5 %)
brasero (libisofs)DEBUG : Processed 1116 of 11158 KB (10 %)
brasero (libisofs)DEBUG : Processed 1674 of 11158 KB (15 %)
brasero (libisofs)DEBUG : Processed 2232 of 11158 KB (20 %)
brasero (libisofs)DEBUG : Processed 2790 of 11158 KB (25 %)
brasero (libisofs)DEBUG : Processed 3348 of 11158 KB (30 %)
brasero (libisofs)DEBUG : Processed 3906 of 11158 KB (35 %)
brasero (libisofs)DEBUG : Processed 4464 of 11158 KB (40 %)
brasero (libisofs)DEBUG : Processed 5022 of 11158 KB (45 %)
brasero (libisofs)DEBUG : Processed 5580 of 11158 KB (50 %)
brasero (libisofs)DEBUG : Processed 6138 of 11158 KB (55 %)
brasero (libisofs)DEBUG : Processed 6696 of 11158 KB (60 %)
brasero (libisofs)DEBUG : Processed 7254 of 11158 KB (65 %)
brasero (libisofs)DEBUG : Processed 7812 of 11158 KB (70 %)
brasero (libisofs)DEBUG : Processed 8370 of 11158 KB (75 %)
brasero (libisofs)DEBUG : Processed 8928 of 11158 KB (80 %)
brasero (libisofs)DEBUG : Processed 9486 of 11158 KB (85 %)
brasero (libisofs)DEBUG : Processed 10044 of 11158 KB (90 %)
brasero (libisofs)DEBUG : Processed 10602 of 11158 KB (95 %)
brasero (libisofs)DEBUG : Processed 11158 of 11158 KB (100 %)
brasero (libisofs)DEBUG : Writer thread joined

This is with brasero 2.30.3-2 on Squeeze.

There seem to be some indications that the failure is more likely to 
happen with more data, or with more files. I tested with a directory 
called "Data Disk" containing files named "Test File XX" with XX being a 
2-digit number. Each of these files was an identical mp3 file, but the 
more copies I included the more frequently I saw a failure. I'm 
intentionally including spaces in path names because that was the format 
when I originally noticed the failures. I don't have any particular 
reason to think it is necessary, however.

-Kevin





More information about the pkg-gnome-maintainers mailing list