Volume ID string too long for /usr/bin/genisoimage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cdrkit (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: brasero
Using an updated hardy (upgraded from gutsy), I wanted to burn a CD of lots of photos and some videos, organized in many subfolders for a friend of mine.
I tried burning the CD, but it wouldn't work, with brasero giving me an error when it was about to write the data to the disk.
Brasero said, I should check the CD/DVD.
When I tried the other CD/DVD-writer (external, via USB), it wouldn't work either.
Neither did changing the target CD solve the problem.
When even burning to an image file (iso) threw the same error, I decided to have a look into the logs presented with the error.
There, I found the following:
"BraseroGenisoimage stderr: /usr/bin/
... and followed by more "stderr: [...]".
The original Volume ID I had entered was "Bilder 4/2008 von Klaus für Ines", which is, afaik, the maximum length as restrained by brasero.
After changing the Volume ID to "4/2008 von Klaus für Ines", I could "burn" an iso file as expected, and I could also after that burn the iso file to the CD.
The md5 check failed:
"BraseroMd5sum setting new checksum (type = 1) f0158a3b01cfa10
But none of the ~570 photos are broken. There are some short AVIs on the CD that I didn't check, but I think it would be quite a coincidence if a single occuring error was in those avi files, (being maybe ~5% of the disk). So I'm not sure if I can trust brasero here.
Why cdrkit? Shouldn't this be a brasero bug?
I think, brasero's maximum Volume ID string length (maxlength restraint for the input field) is too long. So this is not genisoimage's problem.
cdrkit is just making the rules. Brasero, as their client, has to work with those.