Comment 64 for bug 780117

Dear Andrea, thank you for testing the patch.

Could you please provide more information. Especially the version of Brasero, maybe find out if libburn is really disabled and what is used now. Additionally the versions of the components Brasero depends on and the any log files from Brasero.

It is sad, that upstream at https://bugzilla.gnome.org/show_bug.cgi?id=655601 does give more information. Also it makes it more difficult that this bug is discussed in at least three different places. But the libburnia developers prefer to use mailing lists and additionally it looks like there are some problems how Brasero uses libburnia.

So to fix this once and for all, it would be great if you could join the discussion at #617409 in the Debian BTS. You can easily import the messages by directly downloading the mbox file [2] or by installing the package devscripts

    $ sudo aptitude install devscripts

and executing `bts show --mbox 617409` and import that message to your mail program. That reply to the appropriate message with your findings. For example if I remember correctly Thomas asked to use the command line tool `xorriso` to test if libburn4 is working correctly on with your burner [3]. If that is verified the bug in Brasero using libburn4 should be found and fixed. But the developers definitely need more information for that.

I am sorry, that there does not seem to be an easier way to solve this issue.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617409
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?mbox=yes;bug=617409
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617409#159