nautilus-cd-burner wrongly reports burn failure

screenshot of the error

Thank you for your bug. What do you try to burn on the CD? Could you activate with gconf-editor and then run nautilus-cd-burner from a command line and copy the debug log to a comment?

I usually burn videos (*.avi, *.mp4, *.mkv) as data CD or DVD, but this only happens with CD burning and not DVD burning as I've stated earlier.

I also burned Feisty ISO onto CD with similar results.

Here's console output after enabling debug in gconf-editor. It's pretty long and got truncated.

If you need the untruncated version, i'll do another round.

looks like a cdrecord bug, does it do the same when running "cdrecord fs=16m dev=/dev/scd1 -eject -dao driveropts=burnfree -v -data -nopad /tmp/image.iso.UC8AOT" from a command line?

I'm not familiar with cd burning from console.

Do i just run that command straightaway, or do i have to do something else to generate /tmp/image.iso.UC8AOT beforehand?

you have to create one using mkisofs or copy the one created with nautilus-cd-burner while it's running

thanks. here's the output from running "cdrecord fs=16m dev=/dev/hdb -eject -dao driveropts=burnfree -v -data -nopad test.iso"

marking unconfirmed, I'm too busy to work on that and don't get the bug, nautilus-cd-burner calls the same command, it's weird it doesn't act the same way then

Do you still have the bug?

I can't tell. A series of system lockups after beta forced me to clean install Edgy. I can't seem to access the main site & wiki easily recently so I've been waiting to get back into Feisty (unsuccessfully).

I've got to remember to keep a proper copy of the install CD on hand when testing stuff :-(

Was about to report the same bug....

fresh feisty install, nautilus complains. But a CD self check showed the the CD is alright.

I am getting the same bug here. If i remember correctly i had it in edgy also but either way it is here currently in feisty. Sometimes my cds burn correctly and sometimes they don't. In windows cds burn without error so i think it is not a hardware issue.

Same bug for me too.
The cd is correctly burned.

Could you get a debug log?

Tell me how or point me to a link and id love to.

use gconf-editor, activate /apps/nautilus-cd-burner/debug, run nautilus-cd-burner on a command line

Am I crazy? I don't know where to find the debug log. I ran this command
cdrecord fs=16m dev=/dev/cdrw -eject -dao driveropts=burnfree -v -data -nopad '/media/media/ubuntu-7.04-desktop-i386.iso'
and burned it burned a cd with no apparent error. But again the location of the debug log is unknown to me. :~)
I will keep searching

Log attached

I see the light! man that took to long to figure out
Question: I have done this twice now. The first time there was a new cdrecord line for every single mb written. This was a problem because the terminal apparently does not store 700 lines so i could not go back and copy the first part of the log. The second time as you can see in the attachment it did the same thing at first but then at 29Mb it jumped to 71Mb and finally to 699MB. Even more interesting to me is the fact that the 29 and 79mb lines are unfinished. This is prolly entirely unrelated but i found it interesting.

Is there a way to make the terminal remember more or log of some sort that stores that info??
thanxs

you can run "nautilus-cd-burner &>log" to direct them to log

Log attached

Douglas, you get a failure error when getting this log?

Yes I receive a dialog box at the end of the burn saying there were errors try again at a lower speed.

The original screenshot attached to this bug by Tan is identical to the error I receive.

The md5sum of resulting burned iso matches source and I have no conclusive proof that the burn was indeed bad.

In my review of the log files attached makes me suspect the sense key error after sending CUE sheet is the problem. I have another feisty install which I compared logs to that does not have this issue and that was the only resultant difference I observed.

It may be worth noting I have a SATA board and using libata which from other bug reports appears to have issues blanking CDRW and other issues. While I was not using or blanking a CDRW it may be another piece in the puzzle.

I updated firmware on the Sony DVD RW DRU-810A for grins and it did not remedy the issue.

Running the cdrecord command directly produces the same log file.

My apologies for not including this information on previous comment. I'm still a bit new at launchpad.

same behaver here on feisty and debian/sid

nautilus-cd-burner reports error: "There was an error writing to the disc:Error while writing to disc. Try a lower speed" , even tough the burn was successful.

I did not try anything else apart of isos. Right click on *.iso and "Write to disk ..." by doing this every time I got this error.

There is a similar bug on http://bugzilla.gnome.org/show_bug.cgi?id=390634

The log has a "cdrecord stderr: Sense flags: Blk 0 (not valid) " which seems to trigger the error

Hello, i have the same problem of wrongly error report, but when a CD image finish burning.

Burning a cd image (.iso) consistently gives me this write error, then suggests a lower write speed. However, the md5sums match perfectly.

I guess this is not a problem of nautilus-cd-burner but the error is in hal (libhal1 or hal1).
Check if you can select in the nautilus-burn dialog an appropiate speed. For me it isn't possible since Gutsy, only weird speed selections beginning with 9x. Therefore the error gets produced.

See this bug report: https://bugs.launchpad.net/ubuntu/+source/hal/+bug/67034

upstream bug comment

"That's a bug in wodim for wobbling. The burnt CD might be working, but if
wodim's right, it's not recorded as intended though."

I've been having the exact same error in Intrepid Ibex 8.10. Before I realized that it was actually burning good CDs, I'd thrown away what I thought were 'coasters.'

What information can I provide in order to help troubleshoot?

I haven't had this problem with any prior versions of Ubuntu.

The upstream gnome bug mentions that this is not a gnome problem but exists in wodim for wobbling. A quick search did not bring anything up. Anyone know how to file a bug against this in wodim or wobbling? Neither are familiar to me.

Also can anybody reporte this in jaunty?

In case that the incorrect speed list is derived fom "cdrecord" output,
the incorrect valued are a result from not using cdrecord but
a bastardized variant based on an extremely outdated (nearly
4 year old) cdrecord.

The original cdrecord correctly reports the speed values.

The problem reported by Chris Wald is definitely caused by this
broken cdrecord fork.

I recommend to try recent original software from:

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

compile and install, the latter by calling "make install" as root.

Note that the fork is in conflict with GPL and the Copyright law
and cannot be legally distributed.

This bug is very old, is it still an issue in current Ubuntu version?

I'm no longer seeing this in Ubuntu 12.10 amd64