[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 16:04:52 UTC 2012

On Thursday 05 July 2012 12:37:02 Thomas Schmitt wrote:
> Hi,
> Josselin Mouette wrote:
> > That would be brasero-list:
> > https://mail.gnome.org/mailman/listinfo/brasero-list
> Is there a chance that we could work together to find out what's wrong ?
> If not George Danchev's patch already brings insight, that is.

Thomas (or anyone else), could you please try brasero on your squeeze box (I 
currently don't have any burners at reach), at least the bug claims brasero 
version: 2.30.3-2. Reporters also claim: "I think it only fails if you select 
the option to burn a data project directly from disk. Burning
iso images works."

Then try to apply the patch at:
(this is against brasero-3.4.1, but the change is easy to adapt) and re-run.

I have the impression that the exit status of growisofs child is incorretly 
inspected via WEXITSTATUS (status), half way the burning task completes and 
way before growisofs actually returns success. I think growisofs is signalled 
(could be SIGPIPE or something more brutal)

I also forgot to inspect waitpid() returning -1, but I don't actually think 
this is the case since this would return true anyway.

> Released libisofs-1.2.2 would be a good test bed.
> Of course we could also use libisofs SVN which currently is moving
> towards the next release 1.2.4 and already got some testing.

I'm not at all convinced that libisofs itself is to blame. Brasero libisofs, 
and growisofs plugins is another matter.

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

More information about the Pkg-libburnia-devel mailing list