Brasero fails to burn cue/bin file due to missing -dao within wodim

Bug #497048 reported by Tworkemon on 2009-12-15
84
This bug affects 16 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: brasero

Package: brasero
Version: 2.28.2-0ubuntu1
Ubuntu Karmic

Error shown as follows:

Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1848)
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_set_output_size_for_current_track
BraseroBurnURI stopping
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_session_output_size
BraseroBurnURI output set (IMAGE) image = /tmp/brasero_tmp_7X4O4U.bin toc = /tmp/brasero_tmp_7X4O4U.cue
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_current_track
BraseroBurnURI no burn:// URI found
BraseroBurnURI stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_set_output_size_for_current_track
BraseroLocalTrack stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_session_output_size
BraseroLocalTrack output set (IMAGE) image = /tmp/brasero_tmp_C6UA5U.bin toc = /tmp/brasero_tmp_C6UA5U.cue
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_current_track
BraseroLocalTrack no remote URIs
BraseroLocalTrack stopping
BraseroWodim called brasero_job_get_action
BraseroWodim getting varg
BraseroWodim called brasero_job_get_action
BraseroWodim got varg:
BraseroWodim deactivating
BraseroWodim called brasero_job_get_action
BraseroWodim getting varg
BraseroWodim called brasero_job_get_action
BraseroWodim called brasero_job_get_device
BraseroWodim called brasero_job_get_flags
BraseroWodim called brasero_job_get_speed
BraseroWodim called brasero_job_get_flags
BraseroWodim called brasero_job_get_input_type
BraseroWodim called brasero_job_get_fd_in
BraseroWodim called brasero_job_get_current_track
BraseroWodim called brasero_job_set_current_action
BraseroWodim got varg:
 wodim
 -v
 dev=/dev/sr0
 speed=24
 fs=16m
 cuefile=/home/user/FILE.CUE
BraseroWodim Launching command
BraseroWodim called brasero_job_get_fd_out
BraseroWodim stderr: wodim: The cuefile= option only works with -dao.
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: Usage: wodim [options] track1...trackn
BraseroWodim called brasero_job_get_flags
BraseroWodim stdout: HUP
BraseroWodim stderr:
BraseroWodim stderr: Use wodim -help
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: to get a list of valid options.
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr:
BraseroWodim stderr: Use wodim blank=help
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: to get a list of valid blanking options.
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr:
BraseroWodim stderr: Use wodim dev=b,t,l driveropts=help -checkdrive
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: to get a list of drive specific options.
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr:
BraseroWodim stderr: Use wodim dev=help
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: to get a list of possible SCSI transport specifiers.
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: HUP
BraseroWodim process finished with status 255
BraseroWodim called brasero_job_error
BraseroWodim finished with an error
BraseroWodim asked to stop because of an error
 error = 0
 message = "no message"
BraseroWodim stopping
BraseroWodim got killed
Session error : unknown (brasero_burn_record brasero-burn.c:2811)

If you run wodim with -dao it burns successfully.

affects: brasero (Ubuntu) → cdrkit (Ubuntu)

Run "sudo apt-get install cdrdao" and try again.

Schily (schilling-fokus) wrote :

Be careful! cdrdao does not support all features in CUE files.

Cdrecord is a better choice:

ftp://ftp.berlios.de/pub/cdrecord/alpha/

http://cdrecord.berlios.de/

Michele (mikelito) wrote :

I think the options to wodim has to be changed. Is there a simple way to do so in brasero?
CLI workaround is to run from a terminal EXACTLY the string listed in the log, plus -dao

i.e., in the case of the OP
 wodim -dao -v dev=/dev/sr0 speed=24 fs=16m cuefile=/home/user/FILE.CUE

Michele (mikelito) wrote :

since wodim works fine, and it's only brasero which is passing the wrong options, I'd assign the bug to brasero. Please correct if for some reason there is also a problem with wodim itself.

affects: cdrkit (Ubuntu) → brasero (Ubuntu)
Changed in brasero (Ubuntu):
importance: Undecided → Low
David Huggins-Daines (dhuggins) wrote :

Not exactly sure why this is assigned "Low" importance. It makes it impossible to burn audio CDs.

Daniel Gnoutcheff (gnoutchd) wrote :

I'm having the exact same problem on lucid. Debug log attached. I confirm that running wodim manually with '-dao' added works flawlessly. And before anyone asks, cdrdao is already installed. So I have no good workaround for this.

Furthermore, I do not recall having this problem with karmic. So for me, this bug represents a major regression.

Dag Odenhall (dag.odenhall) wrote :

This bug affects me in Lucid, trying to burn an audio CD with Brasero after failing to do so in Rhythmbox (Bug #459103). Eventually managed to burn the CD by choosing the option to burn directly to the disk without creating an image (or something like that), but the default options out of a fresh Lucid install fails.

Relevant errors:

BraseroWodim got varg:
 wodim
 -v
 dev=/dev/sr0
 speed=20
 fs=16m
 -text
 cuefile=/tmp/brasero_tmp_UNDVBV.cue
BraseroWodim Launching command in /tmp
BraseroWodim called brasero_job_get_fd_out
BraseroWodim stderr: wodim: The cuefile= option only works with -dao.

Cesare Mastroianni (cece) wrote :

The same on Lucid for me as well.

Many thanks for Your help

Ciao from Italy
CM

Useful help. Thanks, all.
For the missing dao problem (Brasero now seems to have a few other issues I have not seen before) I have found you can use gconf-editor to set the dao flag. It is located under apps/brasero/config and is a checkbox.
This is easier than using wodim from the command line.

Pedro Villavicencio (pedro) wrote :

could somebody try the Brasero proposed package ? that might fix the issue here as well. thanks.

piviul (piviul) wrote :

I would like to try the proposed package but... where I can find it?

Piviul

piviul (piviul) wrote :

I'm very sorry for the latest message... it was very simple to install the new proposed update. Well I've installed it but is changed only the error that brasero return: "BraseroWodim asked to stop because of an error".

I attach the full brasero log?field.comment=I'm very sorry for the latest message... it was very simple to install the new proposed update. Well I've installed it but is changed only the error that brasero return: "BraseroWodim asked to stop because of an error".

I attach the full brasero log

Thank you very much

Piviul

piviul (piviul) wrote :

The last logs I've sent are wrong! They are the logs generated from the previous (the "original") version of brasero not the one I've installed from the proposed updates. Now I attach the right logs.

I hope you can forgive me.

Piviul

While waiting for this bug to be fixed, here is a workaround that works for me in Lucid:

In Brasero, select burn to file. Then open Nautilus, navigate to where you saved the file (your home directory is the default), right-click the .cue-file, and select "Write to Disc".

On 05/27/2010 04:59 PM, Pedro Villavicencio wrote:
> could somebody try the Brasero proposed package ? that might fix the
> issue here as well. thanks.

Done, and it's a NAK. Upgrading to brasero from -proposed has no effect.

Pedro Villavicencio (pedro) wrote :

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. Thanks in advance!

Changed in brasero (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers