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 654014 - gnome-control-center crashed with SIGSEGV in g_closure_invoke() (refresh_ui)
gnome-control-center crashed with SIGSEGV in g_closure_invoke() (refresh_ui)
Status: RESOLVED DUPLICATE of bug 677969
Product: gnome-control-center
Classification: Core
Component: Network
3.0.x
Other Linux
: Normal critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-05 14:35 UTC by Pedro Villavicencio
Modified: 2013-04-18 15:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.91/3.0



Description Pedro Villavicencio 2011-07-05 14:35:18 UTC
this report has been filed here:

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

the user was testing the network capplet and it crashed leaving the following backtrace.

Backtrace:

".

Thread 1 (Thread 2032)

  • #0 refresh_ui
    at cc-network-panel.c line 1706
  • #1 g_closure_invoke
    at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c line 771
  • #2 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 3256
  • #3 g_signal_emit_valist
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 2987
  • #4 g_signal_emit
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 3044
  • #5 g_closure_invoke
    at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c line 771
  • #6 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 3256
  • #7 g_signal_emit_valist
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 2987
  • #8 g_signal_emit
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 3044
  • #9 device_state_changed
    at nm-device.c line 332
  • #10 marshal_dbus_message_to_g_marshaller
    at dbus-gproxy.c line 1733
  • #11 g_closure_invoke
    at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c line 771
  • #12 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 3256
  • #13 g_signal_emit_valist
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 2987
  • #14 g_signal_emit
    at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c line 3044
  • #15 dbus_g_proxy_emit_remote_signal
    at dbus-gproxy.c line 1786
  • #16 dbus_g_proxy_manager_filter
    at dbus-gproxy.c line 1353
  • #17 dbus_g_proxy_manager_filter
    at dbus-gproxy.c line 1194
  • #18 dbus_connection_dispatch
    at dbus-connection.c line 4647
  • #19 message_queue_dispatch
    at dbus-gmain.c line 90
  • #20 g_main_dispatch
    at /build/buildd/glib2.0-2.29.8/./glib/gmain.c line 2477
  • #21 g_main_context_dispatch
    at /build/buildd/glib2.0-2.29.8/./glib/gmain.c line 3050
  • #22 g_main_context_iterate
    at /build/buildd/glib2.0-2.29.8/./glib/gmain.c line 3128
  • #23 g_main_loop_run
    at /build/buildd/glib2.0-2.29.8/./glib/gmain.c line 3336
  • #24 gtk_main
    at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkmain.c line 1363
  • #25 g_application_run
    at /build/buildd/glib2.0-2.29.8/./gio/gapplication.c line 1326
  • #26 main
    at control-center.c line 180

Comment 1 Matthias Clasen 2012-06-28 03:06:40 UTC
This could well be a duplicate of bug 677969
Comment 2 Bastien Nocera 2013-04-18 15:27:37 UTC
I'll close this as a duplicate, please reopen if the problem still happens.

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