gnome-control-center crashed with SIGSEGV in refresh_ui()

Bug #805376 reported by hu on 2011-07-04
390
This bug affects 78 people
Affects Status Importance Assigned to Milestone
gnome-control-center
Fix Released
Critical
gnome-control-center (Ubuntu)
High
Unassigned

Bug Description

gnome-control-center crashed with SIGSEGV in g_closure_invoke

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.0.2-1ubuntu7
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic x86_64
Architecture: amd64
Date: Mon Jul 4 17:07:14 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=zh_CN:zh:en_US:en
 PATH=(custom, user)
 LANG=zh_CN.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f08b482b647: mov 0x10(%rbx),%rdi
 PC (0x7f08b482b647) ok
 source "0x10(%rbx)" (0xaaaaaaaaaaaaaaba) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libnetwork.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

hu (river-hu) wrote :

StacktraceTop:
 refresh_ui (panel=0x7f08c7e29510) at cc-network-panel.c:1706
 g_closure_invoke (closure=0x7f08c82af490, return_value=0x0, n_param_values=1, param_values=0x7f08c81f2400, invocation_hint=<value optimized out>) at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:771
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x7f08c81b38a0, emission_return=0x0, instance_and_params=0x7f08c81f2400) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3256
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=0x7fffed9d1b48) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:2987
 g_signal_emit (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3044

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
summary: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
+ (refresh_ui)

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=654014

Changed in gnome-control-center (Ubuntu):
status: New → Triaged
Changed in gnome-control-center:
importance: Unknown → Critical
status: Unknown → New
Changed in gnome-control-center (Ubuntu):
importance: Medium → High
summary: - gnome-control-center crashed with SIGSEGV in g_closure_invoke()
- (refresh_ui)
+ gnome-control-center crashed with SIGSEGV in refresh_ui()
tags: added: precise
tags: added: quantal
Andrei (0p-andrei) wrote :

The patch https://bugzilla.gnome.org/attachment.cgi?id=217473 mentioned in https://bugzilla.gnome.org/show_bug.cgi?id=654014 (linked bug 677969 ) seems to work. I don't get any more crashes from gnome-control-panel (network module).

tags: added: bugpattern-needed
Pablo Catalina (xkill) wrote :

I just opened google-chrome, then try to change the "Proxy Settings" from google chrome advanced settings. The it crashed 2 seconds after Network manager was displayed.

Changed in gnome-control-center:
status: New → Invalid
Tim Lunn (darkxst) wrote :

This bug appears to have been fixed in 2012. So marking as fix released.

Changed in gnome-control-center:
importance: Critical → Unknown
status: Invalid → Unknown
Changed in gnome-control-center (Ubuntu):
status: Triaged → Fix Released
Changed in gnome-control-center:
importance: Unknown → Critical
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.