Dear Debian Brasero 3.x users,
I am CCing you all, but just reply to Tsu’s last message. Unfortunately
all of your replies are not threaded correctly increasing work for the
maintainers and people wanting to help. In the future, it would be
awesome if you could follow the guide in the Wiki [1]. Please make sure
to always CC all people involved in the bug thread.
I am pretty sure for all the people following up here having issues with
Brasero 3.x are experiencing bug #688229 [4].
Am Montag, den 10.09.2012, 18:58 +0430 schrieb Tsu Jan:
> The bug may be related to how Brasero uses libburnia+libisofs.
For those with 3.x, it indeed was such a bug [2] and it is fixed now
[3][4].
It would be helpful if you could test Brasero 3.4.1-4. Please start it
with
$ brasero -g | tee `date +%Y%m%d-%H%M`--brasero.log
to capture the debugging output too. Debugging logs are important as
otherwise nothing can be done about a bug. If you are still experiencing
some issue, please submit a new report with the above log attached.
[…]
Thanks,
Paul
[1] http://wiki.debian.org/BTS/FollowUpOnReports#preview
[2] https://bugzilla.gnome.org/show_bug.cgi?id=685983
[3]
http://git.gnome.org/browse/brasero/commit/?id=253031b69c5dcbcf079c445ec530afb7ccd9ea82
[4] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688229
signature.asc
Description: This is a digitally signed message part
