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 644011 - Trying to run Brasero twice leads to a crash of the primary instance
Trying to run Brasero twice leads to a crash of the primary instance
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
2.32.x
Other Linux
: Normal critical
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
: 636431 665934 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-03-06 09:35 UTC by Alex Băluț
Modified: 2011-12-11 13:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alex Băluț 2011-03-06 09:35:16 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)
Comment 1 Luis Medinas 2011-03-07 01:15:35 UTC 
Brasero isn't suppose to run twice. We forced Brasero to have only one instance running.
Comment 2 Alex Băluț 2011-03-07 06:05:55 UTC 
Ok, but in this case it should not crash, it should bring forward the already running instance.
Comment 3 David King 2011-10-20 14:45:51 UTC 
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!
Comment 4 Alex Băluț 2011-10-20 15:09:00 UTC 
David, please have a look at comment 1 to see what caused the crash of the second instance.
Comment 5 David King 2011-10-20 15:51:08 UTC 
(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.
Comment 6 Alex Băluț 2011-10-20 16:11:17 UTC 
Works now. The first instance does not crash when the second instance is started.
Comment 7 David King 2011-10-20 16:56:22 UTC 
This was probably fixed in the port to GApplication from libunique in Brasero 3.0, so closing as OBSOLETE.
Comment 8 David King 2011-10-20 16:58:07 UTC 
*** Bug 636431 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2011-12-11 13:44:37 UTC 
*** Bug 665934 has been marked as a duplicate of this bug. ***