After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596243 - Brasero doesn't store output of helper programs (cdrecord,growisofs)
Brasero doesn't store output of helper programs (cdrecord,growisofs)
Status: RESOLVED NOTABUG
Product: brasero
Classification: Applications
Component: general
git master
Other Linux
: Normal major
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-09-24 22:10 UTC by Maxim Levitsky
Modified: 2009-09-27 12:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Maxim Levitsky 2009-09-24 22:10:02 UTC 
I am marking this as a major severity bug, since I have lost 3 DL disks, and was presented with useless brasero output.
Comment 1 Philippe Rouquier 2009-09-26 12:59:35 UTC 
Thanks for the report. I don't understand it here. Brasero does include the debug statements from underlying backends. True, it's probably lost in lots of messages (mainly from brasero itself) but it does. Or maybe you're unaware of the existence of options -g and --brasero-media-debug (specifically for the debug of brasero drive/medium probing).
Comment 2 Philippe Rouquier 2009-09-27 12:10:59 UTC 
As per comment on brasero ML. I'm closing it.
NOTE: as for your question is the output stored without -g and --brasero-media-debug, the answer is yes, it is in a temp file stored in the chosen temp directory; the file should be brasero_tpm_{6 letters/numbers}. This file will be used in case the session fails and presented to the user. Once the BraseroSession object is finalized (when you change the project view), the file is destroyed.
So you can indeed see the output of the session even when it succeeds.