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 672930 - gnome-control-center crashed with SIGSEGV in refresh_ui()
gnome-control-center crashed with SIGSEGV in refresh_ui()
Status: RESOLVED DUPLICATE of bug 672922
Product: gnome-control-center
Classification: Core
Component: Network
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-27 15:35 UTC by Sebastien Bacher
Modified: 2012-11-29 15:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2012-03-27 15:35:53 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/912948

"stacktrace from 3.2.2, the bug has duplicates from recent 3.3 version as well

+ Trace 229964

  • #0 refresh_ui
    at cc-network-panel.c line 2205
  • #1 g_cclosure_marshal_VOID__VOID
    at /build/buildd/glib2.0-2.31.6/./gobject/gmarshal.c line 85
  • #2 g_closure_invoke
    at /build/buildd/glib2.0-2.31.6/./gobject/gclosure.c line 774
  • #3 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3302
  • #4 g_signal_emit_valist
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3033
  • #5 g_signal_emit
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3090
  • #6 net_object_emit_changed
    at net-object.c line 51
  • #7 state_changed_cb
    at net-device.c line 45
  • #8 _nm_marshal_VOID__UINT_UINT_UINT
    at nm-marshal.c line 353
  • #9 g_closure_invoke
    at /build/buildd/glib2.0-2.31.6/./gobject/gclosure.c line 774
  • #10 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3302
  • #11 g_signal_emit_valist
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3033
  • #12 g_signal_emit
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3090
  • #13 device_state_changed
    at nm-device.c line 334
  • #14 _nm_marshal_VOID__UINT_UINT_UINT
    at nm-marshal.c line 353
  • #15 marshal_dbus_message_to_g_marshaller
    at dbus-gproxy.c line 1734
  • #16 g_closure_invoke
    at /build/buildd/glib2.0-2.31.6/./gobject/gclosure.c line 774
  • #17 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3302
  • #18 g_signal_emit_valist
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3033
  • #19 g_signal_emit
    at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c line 3090
  • #20 dbus_g_proxy_emit_remote_signal
    at dbus-gproxy.c line 1787
  • #21 dbus_g_proxy_manager_filter
    at dbus-gproxy.c line 1354
  • #22 dbus_g_proxy_manager_filter
    at dbus-gproxy.c line 1195
  • #23 dbus_connection_dispatch
    at ../../dbus/dbus-connection.c line 4603
  • #24 message_queue_dispatch
    at dbus-gmain.c line 90
  • #25 g_main_dispatch
    at /build/buildd/glib2.0-2.31.6/./glib/gmain.c line 2513
  • #26 g_main_context_dispatch
    at /build/buildd/glib2.0-2.31.6/./glib/gmain.c line 3050
  • #27 g_main_context_iterate
    at /build/buildd/glib2.0-2.31.6/./glib/gmain.c line 3121
  • #28 g_main_context_iterate
    at /build/buildd/glib2.0-2.31.6/./glib/gmain.c line 3058 






Comment 1


Sebastien Bacher





          2012-03-27 15:36:15 UTC
        



similar bug on the fedora tracker: https://bugzilla.redhat.com/show_bug.cgi?id=700528






Comment 2


Sebastien Bacher





          2012-04-17 19:16:22 UTC
        



That's still an issue with GNOME 3.4, see i.e
https://launchpadlibrarian.net/99264205/Stacktrace.txt
on https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/970115

Similar bugs on the fedora bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=700528
https://bugzilla.redhat.com/show_bug.cgi?id=696117
https://bugzilla.redhat.com/show_bug.cgi?id=799843

The bug seems to be collecting quite some duplicates on different bugs trackers






Comment 3


Mathieu Trudel-Lapierre





          2012-04-27 15:59:23 UTC
        



Could this be related/pretty much a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=672922 ?

I'm using what seems to be like the most likely way to get this crash, and all I'm hitting is a crash in panel_get_strongest_unique_aps() now; with the patch applied, I haven't been able to make the panel crash at all yet.






Comment 4


Bastien Nocera





          2012-11-29 15:51:30 UTC
        



Let's make it a dupe.

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