burnproof should be enabled by default

[Uphaar Agrawalla]

On some CD burners, the CD-burning process finishes improperly if burnproof is
not enabled, rendering the disc mostly useless. I found this out the hard way,
after having wasted 6 CDs experimenting where's the issue.

This is what happens:
The burning starts, continues for a while and then suddenly you see n-c-b's
status bar jump to the "Fixating" stage, even though the data has not been
burned completely. It happens at various random times, like after 20%, 30%, 50%
or 80% of the data has been written. The resulting CD is readable, but with only
partial data, it is useless if it is a single file.

Resolution:
Have burnproof enabled by default ( /apps/nautilus-cd-burner/burnproof in gconf
). With this set, all CDs burn fine.

Note: This is not limited to n-c-b only, I had tried with graveman, coaster,
gnomebaker too and without burnproof they also produce coasters.

[Sebastien Bacher (seb128)]

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

[Sebastien Bacher (seb128)]

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

[Uphaar Agrawalla (uphaar)]

Great, thanks seb :-)

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

[Sebastien Bacher (seb128)]

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.

[Daniel Holbach (dholbach)]

Why is this bug still open?

[Sebastien Bacher (seb128)]

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?"

[Daniel Holbach (dholbach)]

Can you please answer Sébastien's question?

[Sarah Kowalik (hobbsee-deactivatedaccount)]

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.