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 657469 - gnome-control-center crashed with SIGSEGV in g_type_check_is_value_type()
gnome-control-center crashed with SIGSEGV in g_type_check_is_value_type()
Status: RESOLVED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: Display
3.1.x
Other Linux
: Normal critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
3.10
Depends on:
Blocks:
 
 
Reported: 2011-08-26 19:00 UTC by Pedro Villavicencio
Modified: 2014-12-18 01:45 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-08-26 19:00:27 UTC
this report has been filed here:

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

crashed after log in

".

Thread 1 (Thread 0xb78d0840 (LWP 6177))

  • #0 type_check_is_value_type_U
    at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c line 4091
  • #1 g_type_check_is_value_type
    at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c line 4120
  • #2 g_value_type_compatible
    at /build/buildd/glib2.0-2.29.16/./gobject/gvalue.c line 499
  • #3 g_value_object_collect_value
    at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 3073
  • #4 g_object_new_valist
    at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 1597
  • #5 g_object_new
    at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c line 1325
  • #6 gnome_rr_config_new_current
    at gnome-rr-config.c line 733
  • #7 on_screen_changed
    at xrandr-capplet.c line 159
  • #8 g_cclosure_marshal_VOID__VOID
    at /build/buildd/glib2.0-2.29.16/./gobject/gmarshal.c line 85
  • #9 g_closure_invoke
    at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 773
  • #10 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3271
  • #11 g_signal_emit_valist
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3002
  • #12 g_signal_emit
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3059
  • #13 screen_update
    at gnome-rr.c line 672
  • #14 screen_on_event
    at gnome-rr.c line 698
  • #15 screen_on_event
    at gnome-rr.c line 678
  • #16 gdk_event_apply_filters
    at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 83
  • #17 gdk_event_source_translate_event
    at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 204
  • #18 _gdk_x11_display_queue_events
    at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 334
  • #19 gdk_display_get_event
    at /build/buildd/gtk+3.0-3.1.12/./gdk/gdkdisplay.c line 311
  • #20 gdk_event_source_dispatch
    at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 356
  • #21 g_main_dispatch
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 2439
  • #22 g_main_context_dispatch
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3008
  • #23 g_main_context_iterate
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3086
  • #24 g_main_loop_run
    at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3294
  • #25 gtk_main
    at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkmain.c line 1367
  • #26 gtk_application_run_mainloop
    at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkapplication.c line 112
  • #27 g_application_run
    at /build/buildd/glib2.0-2.29.16/./gio/gapplication.c line 1325
  • #28 main
    at control-center.c line 193

Comment 1 Thomas Wood 2013-09-05 13:25:18 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Comment 2 André Klapper 2014-12-18 01:45:34 UTC
Hi Pedro, 
I am closing this bug report as no updated information has been provided.
Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.