GNOME Bugzilla – Bug 368493
Don't create toc sheet with absolute path / better error message
Last modified: 2009-07-29 10:45:57 UTC
The toc file created when making a copy of an audio cd contains the full path to the iso file. This will create trouble if a user moves the files and later tries to burn them. Simply assuming that the iso file is in the same dir as the toc file would solve this problem. On a similar note, when n-c-b notices that the iso/bin file is missing from the cue/toc file, the user gets a general error message with no real information. An error message informing the user about the missing file would be good, an open file dialogue window letting the user find the missing file would be even better.
Yeah. Any chance you can make a patch for this too? :)
I did a little more investigation, and it turns out that cdrdao is to blame for writing toc files with an absolute path. I will file a bug about this with them. I can probably write a patch so n-c-b shows an error message when cdrdao can't find the toc / cue sheet. There are two error messages from cdrdao, related to this: ERROR: Could not find input file "data.bin". ERROR: Cannot open data file "/foo/bar/data.bin": No such file or directory What's the best solution here, simply to add these strings to cdrdao_stderr_line and pass the error message on to the user?
Yes that seems like a reasonable approach. Please do file a bug with cdrdao and with your OS distro. Thanks.
There are three different error messages when dealing with missing files in cue / toc files. Depending on if cdrdao doesn't find the file, if the path is wrong and depending on if it's a data or audio image. ERROR: Could not find input file "bootcd.bin". ERROR: Track 1: Cannot open data file "/home/sa/data.bin": No such file or directory ERROR: Track 1: Cannot open audio file "/home/sa/image.iso": No such file or directory I actually tried to write a patch to check for these, but my meagre skills could only ever get the first string to be matched :)
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.