burnproof should be enabled by default

Thanks your bug. The upstream bugzilla has a comment about why it's not
activated by default: http://bugzilla.gnome.org/show_bug.cgi?id=137099

I'm not sure than changing this default is a good idea, cdrecord guys probably
know what they are doing. You can try to mail the ubuntu-devel mailing list to
get some opinion on this though

I've pinged upstream about this again, they are changing the default for data
which should fix this issue

Great, thanks seb :-)

afaik n-c-b can only burn data CDs - so it can't be an issue at all.

This upload fixes the issue:

 nautilus-cd-burner (2.11.4-0ubuntu1) breezy; urgency=low
 .
   * Sync with Debian.
   * New upstream version:
     - Use burnproof by default when recording data (Ubuntu: #12017).
     - Ask to create another copy after each copy is made.
     - Remove the temporary disc image on error.
     - Use a better error message for filename encoding errors.
   * debian/control.in:
     - updated for the soname change.
   * debian/watch:
     - updated.

Why is this bug still open?

Daniel, it's still open because apparently upstream broke the change when merging some new code

Comment from upstream:

"I'm not sure that this is correct. We should always use it for anything burned
from n-c-b using the cdrecord backend:

        if (TRUE) {
                operation->priv->record_flags |=
NAUTILUS_BURN_RECORDER_WRITE_BURNPROOF;
        }
                if (flags & NAUTILUS_BURN_RECORDER_WRITE_BURNPROOF) {
                        g_ptr_array_add (argv, "driveropts=burnfree");
                }

Can you include the debug output when running to show that it isn't getting
set?"

Can you please answer Sébastien's question?

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.