GNOME Bugzilla – Bug 620467
Brasero burns corrupted data CD
Last modified: 2010-07-29 12:27:01 UTC
Steps : - create a data CD - add files - burn (lowest speed) - eject CD - enter CD => The CD can't be read. It just worked with Xfburn, so I assume the CD-burner is not guilty. The first time it happened (a few days ago, with a slightly older version of brasero) I had just burnt a data DVD with success with the same brasero version. I file the bug as critical since on my computer it makes the most common feature unusable. When the CD is entered, the syslog goes like this : Jun 3 12:08:50 bouzin kernel: [ 6657.047272] UDF-fs: No VRS found Jun 3 12:08:50 bouzin kernel: [ 6657.047287] UDF-fs: No partition found (1) Jun 3 12:08:50 bouzin kernel: [ 6657.076250] ISO 9660 Extensions: Microsoft Joliet Level 3 Jun 3 12:08:50 bouzin kernel: [ 6657.152997] ISO 9660 Extensions: RRIP_1991A Jun 3 12:11:05 bouzin kernel: [ 6792.244924] sr 1:0:1:0: [sr0] Unhandled sense code Jun 3 12:11:05 bouzin kernel: [ 6792.244937] sr 1:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jun 3 12:11:05 bouzin kernel: [ 6792.244947] sr 1:0:1:0: [sr0] Sense Key : Blank Check [current] Jun 3 12:11:05 bouzin kernel: [ 6792.244958] sr 1:0:1:0: [sr0] Add. Sense: No additional sense information Jun 3 12:11:05 bouzin kernel: [ 6792.244969] sr 1:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00 Jun 3 12:11:05 bouzin kernel: [ 6792.244987] end_request: I/O error, dev sr0, sector 0 Jun 3 12:11:05 bouzin kernel: [ 6792.245002] Buffer I/O error on device sr0, logical block 0 Attaching relevant part of syslog, as well as brasero's log. (The only logging I got of Xfburn is the following : ** Message: Using Thunar-VFS 1.0.1 ** Message: Using HAL ** Message: Using Transcodeur GStreamer transcoder.)
Created attachment 162640 [details] /var/log/syslog Shows errors when entering burnt CD.
Created attachment 162641 [details] brasero's debug logging Obtained through "brasero -g > log 2>&1"
Thanks for the report. This seems to be a problem with your wodim/genisoimage version. I had a look at the log and everything seems fine from start to end (correct options for genisoimage and wodim, no error message from any of them)... except the disc of course. What makes me think that is the fact that xfburn manages to burn your discs and xfburn uses libburn/libisofs not wodim/genisoimage. So here is a test (use a CDRW): try to install brasero libburn plugin (it seems to be missing) and retry to burn a data disc. If my assumptions are right it should work this time. Btw, what is your distro? Because if the above is right you may want to file a bug against wodim/genisoimage.
I'm running an up-to-date (X)ubuntu. brasero versino is 2.30.1 I don't know how to install/activate brasero libburn plugin. Packets installed : brasero brasero-common libbrasero-media0 libburn4 Now, in brasero's plugin manager : I can't unckeck wodim (perhaps because it is the only such backend activated) I can't uncheck genisoimage I see neither libburn nor libisofs I can't check cdrdao (says installed version is too old) I can't check cdrecord (says it's a symlink to another program) I can't check mkisofs (says it's a symlink to another program) Sorry for the assistance request. If we can spot the issue and if it is distro related, I'll be happy to go through the pain of finding my way in launchpad's labyrinth to file a bug against incriminated xubuntu packages. Thanks !
As far as I understand from https://bugzilla.gnome.org/show_bug.cgi?id=595034#c22, brasero does not use symlinked versions of backends. Then should we file a bug against Ubuntu for packaging the backends as symlinks ? Or should brasero just skip this test ? (After all, we could leave that up to the packagers, or the user. I don't understand that protection machanism.) Is there anything else I could do to - help resolving this issue or at least spotting it more accurately ? - be able to create data CDs with brasero ?
Hi. I ran tests on a RW CD, between brasero (wodim), and Xfburn (libburn) TAO and SAO : Brasero 0/3 (TAO, don't know how to change that) Xfburn TAO 0/3 Xfburn SAO 3/3 (I guess SAO is the default) Therefore the issue is I can't burn TAO. Now I need to figure out why but it's not brasero's fault. It's a pity brasero does not allow to choose between TAO and SAO. Perhaps should I open a bug for that. Marking as NOTGNOME, I hope it is appropriate.