[Pkg-libburnia-devel] Bug#617409: brasero: Brasero corrupts all blank CD-R when burning

Fri Jul 6 16:32:13 UTC 2012

Hi

Sorry I'm overstrained by the Debian infrastructure. ;-) I hit all the
reportbug crasher bugs too...

But anyway, I updated to brasero 3.4.1 and I can still reproduce the bug.

I used a CD-RW and created a data project with one folder with two files
in it (about 300MB). I enabled on-the-fly burning (see screen shot). It
burned, reported success and failed to eject the CD. The CD contains no
valid file system and it can not be mounted. Brasero is also unable to
clear the CD. I have to use K3B to format it (strange!).

Notes:
- Disabling the option "Burn the image directly without saving to disc"
(see screen shot) creates a working CDs (that can be ejected
automatically too).
- Burning ISO images with brasero works fine. Just today I burned a
Debian and an Ubuntu image without problems.
- Kernel: Linux 3.2.0-2-amd64

I hope this helps.

I will have a look at xorriso... the manpage looks horrible. Any
specific parameters I should test?

Cheers
Simon

simon at beutelteufel:~$ brasero
brasero (libisofs)DEBUG : Creating low level ECMA-119 tree...
brasero (libisofs)DEBUG : Matching hardlinks...
brasero (libisofs)DEBUG : Sorting the low level tree...
brasero (libisofs)DEBUG : Mangling names...
brasero (libisofs)DEBUG : Creating low level Joliet tree...
brasero (libisofs)DEBUG : Sorting the Joliet tree...
brasero (libisofs)DEBUG : Mangling Joliet names...
brasero (libisofs)DEBUG : Computing position of dir structure
brasero (libisofs)DEBUG : Computing length of pathlist
brasero (libisofs)DEBUG : Computing position of Joliet dir structure
brasero (libisofs)DEBUG : Computing length of Joliet pathlist
brasero (libisofs)DEBUG : Starting image writing...
brasero (libisofs)DEBUG : Write volume descriptors
brasero (libisofs)DEBUG : Write Primary Volume Descriptor
brasero (libisofs)DEBUG : Write SVD for Joliet
brasero (libisofs)DEBUG : Writing ISO Path tables
brasero (libisofs)DEBUG : Writing Joliet Path tables
brasero (libisofs)DEBUG : Writing Files...
brasero (libisofs)DEBUG : Processed 5180 of 103584 KB (5 %)
brasero (libisofs)DEBUG : Processed 10360 of 103584 KB (10 %)
brasero (libisofs)DEBUG : Processed 15538 of 103584 KB (15 %)
brasero (libisofs)DEBUG : Processed 20718 of 103584 KB (20 %)
brasero (libisofs)DEBUG : Processed 25896 of 103584 KB (25 %)
brasero (libisofs)DEBUG : Processed 31076 of 103584 KB (30 %)
brasero (libisofs)DEBUG : Processed 36256 of 103584 KB (35 %)
brasero (libisofs)DEBUG : Processed 41434 of 103584 KB (40 %)
brasero (libisofs)DEBUG : Processed 46614 of 103584 KB (45 %)
brasero (libisofs)DEBUG : Processed 51792 of 103584 KB (50 %)
brasero (libisofs)DEBUG : Processed 56972 of 103584 KB (55 %)
brasero (libisofs)DEBUG : Processed 62152 of 103584 KB (60 %)
brasero (libisofs)DEBUG : Processed 67330 of 103584 KB (65 %)
brasero (libisofs)DEBUG : Processed 72510 of 103584 KB (70 %)
brasero (libisofs)DEBUG : Processed 77688 of 103584 KB (75 %)
brasero (libisofs)DEBUG : Processed 82868 of 103584 KB (80 %)
brasero (libisofs)DEBUG : Processed 88048 of 103584 KB (85 %)
brasero (libisofs)DEBUG : Processed 93226 of 103584 KB (90 %)
brasero (libisofs)DEBUG : Processed 98406 of 103584 KB (95 %)
brasero (libisofs)DEBUG : Processed 103584 of 103584 KB (100 %)

simon at beutelteufel:~$ sudo mount -t iso9660 -r /dev/cdrom /media/cdrom0
mount: wrong fs type, bad option, bad superblock on /dev/sr0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

[22295.543931] ISO 9660 Extensions: Microsoft Joliet Level 3
[22295.597809] ISO 9660 Extensions: RRIP_1991A
[22796.601042] sr 0:0:0:0: [sr0] Device not ready
[22796.601048] sr 0:0:0:0: [sr0]  Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[22796.601054] sr 0:0:0:0: [sr0]  Sense Key : Not Ready [current]
[22796.601060] sr 0:0:0:0: [sr0]  Add. Sense: Medium not present
[22796.601067] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 02 00 00
02 00
[22796.601079] end_request: I/O error, dev sr0, sector 8
[22796.601086] Buffer I/O error on device sr0, logical block 1
[22796.605512] sr 0:0:0:0: [sr0] Device not ready
[22796.605515] sr 0:0:0:0: [sr0]  Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[22796.605520] sr 0:0:0:0: [sr0]  Sense Key : Not Ready [current]
[22796.605525] sr 0:0:0:0: [sr0]  Add. Sense: Medium not present
[22796.605532] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 02 00 00
02 00
[22796.605544] end_request: I/O error, dev sr0, sector 8
[22796.605553] Buffer I/O error on device sr0, logical block 1
[22796.606436] sr 0:0:0:0: [sr0] Device not ready
[22796.606439] sr 0:0:0:0: [sr0]  Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[22796.606449] sr 0:0:0:0: [sr0]  Sense Key : Not Ready [current]
[22796.606454] sr 0:0:0:0: [sr0]  Add. Sense: Medium not present
[22796.606462] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 02 00 00
02 00
[22796.606474] end_request: I/O error, dev sr0, sector 8
[22796.606482] Buffer I/O error on device sr0, logical block 1
[22796.607453] sr 0:0:0:0: [sr0] Device not ready
[22796.607457] sr 0:0:0:0: [sr0]  Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[22796.607467] sr 0:0:0:0: [sr0]  Sense Key : Not Ready [current]
[22796.607472] sr 0:0:0:0: [sr0]  Add. Sense: Medium not present
[22796.607479] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 04 00 00 00
02 00
[22796.607490] end_request: I/O error, dev sr0, sector 4096
[22796.607499] Buffer I/O error on device sr0, logical block 512
[22796.608254] sr 0:0:0:0: [sr0] Device not ready
[22796.608262] sr 0:0:0:0: [sr0]  Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[22796.608272] sr 0:0:0:0: [sr0]  Sense Key : Not Ready [current]
[22796.608286] sr 0:0:0:0: [sr0]  Add. Sense: Medium not present
[22796.608301] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 04 00 00 00
02 00
[22796.608338] end_request: I/O error, dev sr0, sector 4096
[22796.608347] Buffer I/O error on device sr0, logical block 512
[22796.609692] sr 0:0:0:0: [sr0] Device not ready
[22796.609695] sr 0:0:0:0: [sr0]  Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[22796.609700] sr 0:0:0:0: [sr0]  Sense Key : Not Ready [current]
[22796.609704] sr 0:0:0:0: [sr0]  Add. Sense: Medium not present
[22796.609717] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 0e 00 00
02 00
[22796.609730] end_request: I/O error, dev sr0, sector 56
[22796.609735] Buffer I/O error on device sr0, logical block 7
[23249.732555] ISOFS: Unable to identify CD-ROM format.

Am 05.07.2012 00:34, schrieb Paul Menzel:
> forwarded 617409 https://bugzilla.gnome.org/show_bug.cgi?id=655601
> tags upstream moreinfo
> quit
>
>
> Dear rpnpif, dear Simon,
>
>
> Am Mittwoch, den 15.02.2012, 00:21 +0100 schrieb Simon Wenner:
>> Here are very similar bug reports in other BTs. Many people are
>> affected:
>>
>> https://bugzilla.gnome.org/show_bug.cgi?id=655601
>> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117
> Simon, thanks for finding these upstream entries. I set the BTS tags
> accordingly. rpnpif, can you confirm that this is the issue you are
> seeing?
>
>> ... and K3B works without any issues. My drive is not broken.
> Reading the listed reports, it looks like this is an error with the
> usage of or an error in libburn4 or libisofs6. I am therefore putting
> the libburnia folks into CC. Maybe they have an idea.
>
> rpnpif, Simon, could you try using `xorriso` [1], which also utilizes
> `libburn4`, to find out if that is a problem with `libburn4`. If it is,
> the bug needs to be reassigned and marked as affecting `brasero` or
> `libbrasero-media3-1`.
>
>
> Thanks,
>
> Paul
>
>
> PS: Simon, in the future could you please CC people from the bug report
> since I guess rpnpif after reporting that bug almost a year before your
> reply does not even know, that you replied. (Of course that could be
> wrong.) In my opinion the best practice is to do the following. Since
> you use a MUA/mail program that should work for you easily.
>
> Use
>
>    $ bts show --mbox 617409
>
> from the package `devscripts` to get all the messages in mbox format.
> Then import this mbox file from 
>
>     ~/.devscripts_cache/bts/
>
> into your mail program from and reply to the appropriate message (reply
> to all). This keeps threading, saves time and you can quote.
>
> To answer to messages you sent, go to your Sent folder and use »Reply to
> all« on that message.
>
>
> [1] http://packages.debian.org/sid/xorriso

-------------- next part --------------
A non-text attachment was scrubbed...
Name: brasero_burn_settings.png
Type: image/png
Size: 24186 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-libburnia-devel/attachments/20120706/1e431c65/attachment-0001.png>