GNOME Bugzilla – Bug 644011
Trying to run Brasero twice leads to a crash of the primary instance
Last modified: 2011-12-11 13:44:37 UTC
When the second Brasero instance is started, Brasero crashes, see below: Output in the 1st terminal window: $ brasero ** (brasero:6674): WARNING **: ERROR loading background pix : Failed to open file '/usr/share/brasero/logo.png': No such file or directory >>>>>>>>Now I'm starting brasero in a different window.<<<<<<<< Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. /home/aleb/6674: No such file or directory. No stack. Output in the 2nd terminal window: $ brasero >>>>>>>>Now I'm closing Ubuntu's "Bug Buddy - Bug reporting tool" window.<<<<<<<< (brasero:6730): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
Brasero isn't suppose to run twice. We forced Brasero to have only one instance running.
Ok, but in this case it should not crash, it should bring forward the already running instance.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
David, please have a look at comment 1 to see what caused the crash of the second instance.
(In reply to comment #4) Alex, a stack trace will tell the developer which function the crash occured on, and more information than the description that you provided in comment 1. a stack trace from both crashes would be very useful.
Works now. The first instance does not crash when the second instance is started.
This was probably fixed in the port to GApplication from libunique in Brasero 3.0, so closing as OBSOLETE.
*** Bug 636431 has been marked as a duplicate of this bug. ***
*** Bug 665934 has been marked as a duplicate of this bug. ***