Hi All, I prepared for generating backtrace in a manner written down here. http://wiki.ubuntu.com/DebuggingProgramCrash However I couldn't start /usr/lib/debug/usr/bin/brasero neither in bash lev@red:~/04$ /usr/lib/debug/usr/bin/brasero bash: /usr/lib/debug/usr/bin/brasero: cannot execute binary file nor in gdb lev@red:~/04$ gdb /usr/lib/debug/usr/bin/brasero 2>&1 | tee ~/gdb-brasero.txt GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/lib/debug/usr/bin/brasero...done. (gdb) set pagination 0 (gdb) handle SIG33 pass nostop noprint Signal Stop Print Pass to program Description SIG33 No No Yes Real-time event 33 (gdb) run Starting program: /usr/lib/debug/usr/bin/brasero /bin/bash: /usr/lib/debug/usr/bin/brasero: cannot execute binary file so I started brasero manually and tried to test if bug still exists. And it seems to be gone. However I don't know if there were any software update since my reporting of this bug. May be some of the libraries on which it relies seem to get a root of this bug solved hiddenly. Anyway. I cannot report on this issue anymore. Levente ps: one more idea! At the time of the reporting. My machine was pretty full of data could it be that brasero cannot generate some auxiliary file and to check the size accordingly? On Wed, Dec 2, 2009 at 3:28 PM, Pedro Villavicencio