Bug 641323 – Trying to open brasero if it is already opens crashes brasero

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 641323 - Trying to open brasero if it is already opens crashes brasero


Summary:	Trying to open brasero if it is already opens crashes brasero


Status:	RESOLVED DUPLICATE of bug 636431

Product:	brasero
Classification:	Applications
Component:	general
Version:	2.32.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	2.26
Assigned To:	Brasero maintainer(s)
QA Contact:	Brasero maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-02-03 09:00 UTC by Ben
Modified:	2011-02-03 09:02 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Ben 2011-02-03 09:00:24 UTC

I am forwarding this downstream bug: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/690897

to reproduce:
1. open brasero
2. repeat
3. watch your first instance of brasero crash.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff43c5411 in g_type_instance_get_private (instance=0x4d4a6dbe, 
    private_type=9962304) at /build/buildd/glib2.0-2.26.0/gobject/gtype.c:4483
4483	/build/buildd/glib2.0-2.26.0/gobject/gtype.c: No such file or directory.
	in /build/buildd/glib2.0-2.26.0/gobject/gtype.c
(gdb) bt

+ Trace 225825

#0 g_type_instance_get_private
at /build/buildd/glib2.0-2.26.0/gobject/gtype.c line 4483
#1 brasero_app_unique_message
at brasero-app.c line 2015
#2 unique_marshal_ENUM__INT_BOXED_UINT
at uniquemarshal.c line 85
#3 g_closure_invoke
at /build/buildd/glib2.0-2.26.0/gobject/gclosure.c line 766
#4 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 3252
#5 g_signal_emit_valist
at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c line 2993
#6 g_signal_emit
#7 unique_app_emit_message_received
at ./uniqueapp.c line 707
#8 unique_factory_dbus_send_message
at uniquefactory-dbus.c line 78
#9 dbus_glib_marshal_uniquebackend_BOOLEAN__STRING_BOXED_UINT_POINTER_POINTER
at uniquebackend-bindings.h line 100
#10 invoke_object_method
at dbus-gobject.c line 1724
#11 object_registration_message
at dbus-gobject.c line 1944
#12 _dbus_object_tree_dispatch_and_unlock
at dbus-object-tree.c line 858
#13 dbus_connection_dispatch
at dbus-connection.c line 4691
#14 message_queue_dispatch
at dbus-gmain.c line 101
#15 g_main_dispatch
at /build/buildd/glib2.0-2.26.0/glib/gmain.c line 2149
#16 g_main_context_dispatch
at /build/buildd/glib2.0-2.26.0/glib/gmain.c line 2702
#17 g_main_context_iterate
at /build/buildd/glib2.0-2.26.0/glib/gmain.c line 2780
#18 g_main_loop_run
at /build/buildd/glib2.0-2.26.0/glib/gmain.c line 2988
#19 IA__gtk_main
at /build/buildd/gtk+2.0-2.22.0/gtk/gtkmain.c line 1237
#20 brasero_app_run_mainwin
at brasero-app.c line 2040
#21 main
at main.c line 129

Comment 1 Akhil Laddha 2011-02-03 09:02:16 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of bug 636431 ***