From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)
Description of problem:
This version of cdrecord is unable to burn BIN/CUE image files, it just prints error messages and does _nothing_:
$ /usr/bin/cdrecord -v gracetime=2 dev=0,0,0 speed=24 -dao driveropts=burnfree cuefile=VIDEOCD.cue -overburn
/usr/bin/cdrecord: No tracks specified. Need at least one.
Usage: /usr/bin/cdrecord [options] track1...trackn
Use /usr/bin/cdrecord -help
to get a list of valid options.
Use /usr/bin/cdrecord blank=help
to get a list of valid blanking options.
Use /usr/bin/cdrecord dev=b,t,l driveropts=help -checkdrive
to get a list of drive specific options.
Use /usr/bin/cdrecord dev=help
to get a list of possible SCSI transport specifiers.
$ man cdrecord
Take all recording related information from a CDRWIN compliant CUE sheet file. No track files are allowed when this option is present and the option -dao is currently needed in addition.
So, as you can see, it seems to be related to incorrect command line parsing - it expects track file even with "cuefile" parameter.
If I recompile the source rpm package without cdrtools-2.01a27-dvd.patch than cdrecord works as expected - burns an image file (it is a _CD_ image, not DVD). My writer is capable of DVD writing also - it is an MSI DVD DUAL 4X drive, may be this causes bad interaction with dvd-patch...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to burn some BIN/CUE image with cdrecord using "cuefile" parameter.
Actual Results: Will do nothing except error report: No tracks specified. Need at least one.
Expected Results: Should burn the image.
Appears to be a dup of bug #119906
*** This bug has been marked as a duplicate of 119906 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.