[Pkg-libburnia-devel] Bug#617409: brasero: Brasero corrupts all blank CD-R when burning (was: additional info)

Thomas Schmitt scdbackup at gmx.net
Thu Jul 5 18:04:29 UTC 2012


George Danchev wrote:
> Thomas (or anyone else), could you please try brasero on your squeeze box (I
> currently don't have any burners at reach),

Ok, for once ... :))
I will cry on your shoulder if it freezes my good old fvwm display.

Actually i avoided trying myself because i do not want to become the
maintainer of Brasero. If it is really orphaned, then so be it.


Ok. First what i can do by comfortable harmless ssh:

  $ su

  # apt-get source brasero
(warns keyblock resource `/root/.gnupg/trustedkeys.gpg': file open error)

  # apt-get build-dep brasero
(Lots of activities)

  # mv check-child-status debian/patches/
  mv: cannot move `check-child-status' to `debian/patches/': No such file or directory

  # mv check-child-status /debian/patches/
  mv: cannot move `check-child-status' to `/debian/patches/': No such file or directory

  # ls check-child-status

Well, i need advise for the patching. 

Unchanged Brasero as installed after above activities:

  $ export DISPLAY=...my.machine...:0.0
  $ brasero &

At least the screen does not burn down ...

  Brasero 2.30.3

Urm. That is not 2.30.3-2. The binary is of November 2010.
I really could need some help with Debian specifics here.

But as we are already at it:
... clicki-di-clonk ...  ... scratching head ... if i use the shell
to learn about the existing files then i can operate the file browser ...
I choose "burn", windows vanish, i see messages from libisofs:
  brasero (libisofs)DEBUG : Processed 366022 of 366022 KB (100 %)

  ** (brasero:7846): WARNING **: Failed to restore the system power manager: The name org.gnome.SessionManager was not provided by any .service files

The big window appears again. In the directory where i started Brasero
is as file
  -rw-r--r--   1 thomas thomas 374806528 Jul  5 18:57 brasero.iso

  # mount -o loop brasero.iso /mnt
Comparing with the original tree 
  $ diff -r /mnt/libburn_dir libburn_dir | less
shows that 322 files are missing of which the names begin by '.'.
This must be due to the way how Brasero traverses the input tree.
My xorriso backups contain every file with all their attributes.

Well, elsewise the image seems ok.

So how do i choose a burner ?
The system is a bit sparsely equipped:
  0  -dev '/dev/sr0' rwrw-- :  'TSSTcorp' 'DVD-ROM SH-D162C' 
  1  -dev '/dev/sr1' rwrw-- :  'TSSTcorp' 'CDDVDW SH-S223B' 

The help text promises
  "7.  The Disc burning setup dialog will be shown"
I get a vanished main window (one could believe it crashed) and a tiny
dialog which offers me to edit "Name: brasero-0.iso", to browse by
"Save in folder:", a "Cancel" button and a "Create Image" button.

Shutting down Brasero, chmod a+rw /dev/sr1, re-starting Brasero.
Now i get a different dialog.
(The device is group "cdrom" to which the user belongs who runs
 Brasero. It is heavily unplausible that Brasero need o+rw.)

I choose: "maximum speed", "Burn the image directly",
but not "Leave the disc open".
Inserted is a DVD+RW.
I see libisofs DEBUG messages ... 70 % ... 100 %
Now it is "checking file integrity". Let me wander to the room
with the machine ... the poor drive is blinking and clonking.
Random access pattern. i'd say.
(libisofs can tell file addresses and one could sort the files by
 that address to get a smooth sequential read pattern.)

I stop the checkread. Will let xorriso do
  xorriso -indev /dev/sr1 -compare_r libburn_dir /libburn_dir
Grrr ... all ownership and permissions differ.
Filtering away those messages
  2>&1 | fgrep -v ' : st_' | fgrep -v 'annot find'
i get no other differences.

Another try with CD-RW:

I click "Burn", it asks whether i really want to blank the disc.
Well, i know what is meant. But wouldn't that confuse novice users ?

It burns ... (i do not know whether libburn is active, but ps shows no
wodim or cdrecord) ... 100 % ... "Finalizing" ... "Success" ...
i abort checkreading, the drive ejects and Brasero is stuck in
"Ejecting medium".
I put it back in. A window pops up and asks me to remove it manually.
I kill Brasero. Enough for today.

Checkreading by xorriso shows only the differences which seem
unavoidable with Brasero.


George: Your shoulder will stay dry. My display survived.

All: Is my Brasero 2.30.3 2005-2010 too old for being buggy ?
If so, could one revert the changes of "2.30.3-2" to see whether it helps ?

In general: How to get the new buggy Brasero ?

Have a nice day :)


More information about the Pkg-libburnia-devel mailing list