Bug 655003 – gnome-control-center crashed with SIGSEGV in gnome_rr_config_load_current()

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


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


Status:	RESOLVED OBSOLETE

Product:	gnome-desktop
Classification:	Core
Component:	libgnome-desktop
Version:	3.1.x
Hardware:	Other Linux

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

URL:
Whiteboard:	3.10

Depends on:
Blocks:

Reported:	2011-07-20 20:29 UTC by Pedro Villavicencio
Modified:	2018-09-21 16:30 UTC

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

Description Pedro Villavicencio 2011-07-20 20:29:30 UTC

this report has been filed here:

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

"I just input a HDMI monitor"

".

+ Trace 227824

Thread 1 (Thread 15047)

#0 gnome_rr_config_load_current
at gnome-rr-config.c line 509
#1 gnome_rr_config_new_current
at gnome-rr-config.c line 735
#2 on_screen_changed
at xrandr-capplet.c line 159
#3 g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.29.10/./gobject/gmarshal.c line 85
#4 g_closure_invoke
at /build/buildd/glib2.0-2.29.10/./gobject/gclosure.c line 773
#5 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c line 3256
#6 g_signal_emit_valist
at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c line 2987
#7 g_signal_emit
at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c line 3044
#8 screen_update
at gnome-rr.c line 666
#9 screen_on_event
at gnome-rr.c line 692
#10 screen_on_event
at gnome-rr.c line 672
#11 gdk_event_apply_filters
at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkeventsource.c line 83
#12 gdk_event_source_translate_event
at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkeventsource.c line 204
#13 _gdk_x11_display_queue_events
at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkeventsource.c line 334
#14 gdk_display_get_event
at /build/buildd/gtk+3.0-3.1.8/./gdk/gdkdisplay.c line 311
#15 gdk_event_source_dispatch
at /build/buildd/gtk+3.0-3.1.8/./gdk/x11/gdkeventsource.c line 356
#16 g_main_dispatch
at /build/buildd/glib2.0-2.29.10/./glib/gmain.c line 2473
#17 g_main_context_dispatch
at /build/buildd/glib2.0-2.29.10/./glib/gmain.c line 3046
#18 g_main_context_iterate
at /build/buildd/glib2.0-2.29.10/./glib/gmain.c line 3124
#19 g_main_loop_run
at /build/buildd/glib2.0-2.29.10/./glib/gmain.c line 3332
#20 gtk_main
at /build/buildd/gtk+3.0-3.1.8/./gtk/gtkmain.c line 1362
#21 gtk_application_run_mainloop
at /build/buildd/gtk+3.0-3.1.8/./gtk/gtkapplication.c line 112
#22 g_application_run
at /build/buildd/glib2.0-2.29.10/./gio/gapplication.c line 1325
#23 main
at control-center.c line 193

Comment 1 GNOME Infrastructure Team 2018-09-21 16:30:56 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-desktop/issues/35.