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

George Danchev danchev at spnet.net
Thu Jul 5 19:36:37 UTC 2012

On Thursday 05 July 2012 20:04:29 Thomas Schmitt wrote:
> Hi,
> 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
>   check-child-status
> Well, i need advise for the patching.

debian/patches is in the unpacked source as brought to you by 'apt-get source 

apt-get source brasero

(this is from my fully updated sid box as of today, your 'stable???' will 

Fetched 3,254 kB in 6s (515 kB/s)                                                                                    
dpkg-source: info: extracting brasero in brasero-3.4.1
dpkg-source: info: unpacking brasero_3.4.1.orig.tar.xz
dpkg-source: info: unpacking brasero_3.4.1-2.debian.tar.gz
dpkg-source: info: applying 03_cue-invalid-frame-75.patch

$ cd brasero-3.4.1/

$ cp /tmp/check-child-status debian/patches/

$ echo check-child-status >> debian/patches/series 

$ cat debian/patches/series 

$ dpkg-checkbuilddeps  # to check you have all build-dependencies installed

$ dpkg-buildpackage

and after that you will shortly see:
dpkg-source: info: applying check-child-status

other patches are applied on unpack/extracting stage by dpkg-source, when you 
ask apt-get source to fetch the source for you.

When finished, see the brasero*.deb in the upper directory (your patched 
package). Remove any previous brasero package you might have:

apt-get --purge remove brasero

install yours:

dpkg -i your_new_brasero*.deb

Use 'gconf-editor' to find brasero plugin configuration, and adjust prioroties. 
Also with a started brasero instance, check Edit | Plugins to see what is in 
use. Finally the log should tell you, since plugins yell some debugging 

Also, reporters claim that just burning ISO image works.
What does not work is "to burn a Data Project directly from disk".

> --------------------------------------------------------------------
> 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.

See what you have installed (^ii means installed)

dpkg -l | awk '$1~/^ii/ && $2~/^brasero/ {print $1 " " $2 " " $3}'


apt-cache policy brasero

(apt-get install brasero - to install from sources configured in sources.list, 
i.e. Debian archive, and: dpkg -i *.deb to install a local deb)

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

On "Burn" you should be able to select one?

> 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.

Hm, you created an ISO and burnt that? I guess we need a "Data Project" as 
reporters claim to be problematic...

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

Hm, it spits messages on its stdout and stderr, doesn't it?

> 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.

Okay, thanks for the try.

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

The initial bug report claims 2.30.3-2 to be buggy, further reports claim this 
bug manifests with newer versions too, up to 3.4.1-2.

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

Get one from Debian stable?

apt-get install brasero

(apt-get install brasero=version also works)

'apt-cache policy brasero' to see your options, depending on your sources.list 
entries. But if you run stable, stay on it for a while :)

pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu>

More information about the Pkg-libburnia-devel mailing list