After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 621828 - wodim error: cuefile= option only works with -dao.
wodim error: cuefile= option only works with -dao.
Status: RESOLVED DUPLICATE of bug 617494
Product: brasero
Classification: Applications
Component: general
2.30.x
Other Linux
: Normal normal
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-06-16 21:51 UTC by Josselin Mouette
Modified: 2010-06-19 19:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Josselin Mouette 2010-06-16 21:51:12 UTC 
Original report: http://bugs.debian.org/580874 from “miguel”.

Excerpt from the session file:

BraseroBurn: (at burn-process.c:142) BraseroWodim got varg:
BraseroBurn: (at burn-process.c:146)    wodim
BraseroBurn: (at burn-process.c:146)    -v
BraseroBurn: (at burn-process.c:146)    dev=/dev/sr0
BraseroBurn: (at burn-process.c:146)    speed=4
BraseroBurn: (at burn-process.c:146)    driveropts=burnfree
BraseroBurn: (at burn-process.c:146)    fs=16m
BraseroBurn: (at burn-process.c:146)    -text
BraseroBurn: (at burn-process.c:146)    cuefile=/tmp/brasero_tmp_LHLCEV.cue
BraseroBurn: (at burn-process.c:623) BraseroWodim Launching command in /tmp
BraseroBurn: (at burn-job.c:1312) BraseroWodim called brasero_job_get_fd_out
BraseroBurn: (at burn-task.c:442) entering loop
BraseroBurn: (at burn-process.c:417) BraseroWodim stderr: wodim: The cuefile= option only works with -dao.
BraseroBurn: (at burn-job.c:1377) BraseroWodim called brasero_job_get_flags
BraseroBurn: (at burn-process.c:417) BraseroWodim stdout: BraseroBurn: (at burn-job.c:1190) BraseroWodim called brasero_job_get_fd_in
BraseroBurn: (at burn-process.c:417) BraseroWodim stderr: Usage: wodim [options] track1...trackn

I think the error message speaks for itself.
Comment 1 Philippe Rouquier 2010-06-19 19:37:27 UTC 
Thanks for the report. This bug has been fixed in the upcoming stable release and in master.

*** This bug has been marked as a duplicate of bug 617494 ***