[gutsy] Brasero burns data CD-R's incorrectly

[Miguel Martinez]

Estimated developers,

Trying to burn data CD-Rs with Brasero results in badly burnt files. However, copying the same files with Nautilus works OK, and ISO's also burn OK. However, creating a data CD-R in brasero and drag-and-dropping files with either nautilus or the integrated file browser will result in files with different md5sums from the original files. According to two forum threads, audio CD's are burnt correctly.

Thanks for your attention.

[Mario Đanić (mario-danic)]

Thank you for your report, Miguel. I know about the problem, and I also have the fix.
I will upload in the coming days.

[Mario Đanić (mario-danic)]

Potential fix in the form of libisofs0.2.5 package is uploaded. Please test, and tell me the results. Thanks.

[Lionel Le Folgoc (mrpouit)]

Hi,

Could you try with the last gutsy revision (0.6.0-2ubuntu1) as soon as it hits the archive?
Thanks.

[Miguel Martinez (el-quark)]

For sure.

However, I have one doubt. Following Luis Medinas' advice in gnome-bugzilla #463174 (link http://bugzilla.gnome.org/show_bug.cgi?id=463174 ) and thanks to a suggestion Mario made me on the forums, I deactivated the libburn backend. Am I supposed to leave it like that or should I reactivate it? Thanks,

Miguel

[Lionel Le Folgoc (mrpouit)]

Hi,

This last revision uses the cdrecord/cdrkit backend, so you can leave it like that.

[Miguel Martinez (el-quark)]

Hi again,

Sorry about the delay. I've just tested Brasero 0.6.0-2ubuntu1 and it burned a data CD well. The md5sum generation went well, as did the ISO generation. Brasero didn't crash when starting to burn the CUE sheet (¿¿??) and the final md5sum check also worked. Furthermore, the speed at which it burned the CD was 10x, the limit of the CD-RW I was using. Browsing the CD via nautilus, everything seems to be OK, and a checksum test I performed went OK.

My brasero options in Gconf:apps/brasero/config are all unchecked with the exception of activate_checksum. In the filter section, all three are checked. I don't know if successful burning was due to package or due to backend deactivation, altough I'm open for more tests. I can also submit the debugging info.

[Lionel Le Folgoc (mrpouit)]

It seems ok. Thanks for the feedback.