Bug 658056 – gnome-control-center crashed with SIGSEGV in gnome_rr_labeler_hide()

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 658056 - gnome-control-center crashed with SIGSEGV in gnome_rr_labeler_hide()


Summary:	gnome-control-center crashed with SIGSEGV in gnome_rr_labeler_hide()


Status:	RESOLVED DUPLICATE of bug 657919

Product:	gnome-control-center
Classification:	Core
Component:	Display
Version:	3.1.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Control-Center Maintainers
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-09-02 13:41 UTC by Pedro Villavicencio
Modified:	2011-09-02 13:47 UTC

See Also:
GNOME target:	---
GNOME version:	3.1/3.2

Description Pedro Villavicencio 2011-09-02 13:41:45 UTC

this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/839093

g-c-c version is 3.1.90

".

+ Trace 228321

Thread 1 (Thread 0xb7872840 (LWP 2161))

#0 gnome_rr_labeler_hide
at gnome-rr-labeler.c line 513
#1 dialog_toplevel_focus_changed
at cc-display-panel.c line 2523
#2 g_cclosure_marshal_VOID__PARAM
at /build/buildd/glib2.0-2.29.16/./gobject/gmarshal.c line 539
#3 g_closure_invoke
at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 773
#4 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3271
#5 g_signal_emit_valist
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3002
#6 g_signal_emit
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3059
#7 g_object_dispatch_properties_changed
at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 925
#8 g_object_notify_dispatcher
at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 331
#9 g_object_notify_queue_thaw
at /build/buildd/glib2.0-2.29.16/./gobject/gobjectnotifyqueue.c line 132
#10 g_object_notify_by_spec_internal
at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 983
#11 g_object_notify
at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 1024
#12 _gtk_window_set_has_toplevel_focus
at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkwindow.c line 9479
#13 gtk_window_focus_out_event
at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkwindow.c line 6080
#14 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkmarshalers.c line 85
#15 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 884
#16 g_closure_invoke
at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 773
#17 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3309
#18 g_signal_emit_valist
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3012
#19 g_signal_emit
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3059
#20 gtk_widget_event_internal
at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkwidget.c line 6126
#21 gtk_main_do_event
at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkmain.c line 1835
#22 _gdk_event_emit
at /build/buildd/gtk+3.0-3.1.12/./gdk/gdkevents.c line 71
#23 gdk_event_source_dispatch
at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 360
#24 g_main_dispatch
at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 2439
#25 g_main_context_dispatch
at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3008
#26 g_main_context_iterate
at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3086
#27 g_main_loop_run
at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3294
#28 gtk_main
at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkmain.c line 1367
#29 gtk_application_run_mainloop
at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkapplication.c line 112
#30 g_application_run
at /build/buildd/glib2.0-2.29.16/./gio/gapplication.c line 1325
#31 main
at control-center.c line 196

Comment 1 Bastien Nocera 2011-09-02 13:47:48 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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