[network]: gnome-control-center crashed with SIGSEGV in refresh_ui()

Bug #1048098 reported by Tom Wright
72
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

The Network Properties page in Gnome Control Centre crashed when the wireless interface was enabled via rfkill in the terminal.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu14
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sun Sep 9 04:22:05 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: gnome-control-center network
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f2e707860b5: mov 0x34(%rbx),%eax
 PC (0x7f2e707860b5) ok
 source "0x34(%rbx)" (0x00000034) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libnetwork.so
 ?? () 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
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: [network]: gnome-control-center crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 23.90-0ubuntu1
 gnome-control-center-signon 0.0.14-0ubuntu1
 indicator-datetime 12.10.0-0ubuntu1

Revision history for this message
Tom Wright (twright-tdw) wrote :
Tom Wright (twright-tdw)
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 refresh_ui (panel=0x7f2e90419620) at cc-network-panel.c:2257
 _g_closure_invoke_va (closure=0x7f2e914cf150, return_value=0x0, instance=0x7f2e914cb590, args=0x7fffe74a32f8, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.33.12/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x7f2e914cb590, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffe74a32f8) at /build/buildd/glib2.0-2.33.12/./gobject/gsignal.c:3211
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.33.12/./gobject/gsignal.c:3356
 g_closure_invoke (closure=0x7f2e914f6060, return_value=0x0, n_param_values=4, param_values=0x7fffe74a35b0, invocation_hint=0x7fffe74a3550) at /build/buildd/glib2.0-2.33.12/./gobject/gclosure.c:777

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: - [network]: gnome-control-center crashed with SIGSEGV in
- g_signal_emit_valist()
+ [network]: gnome-control-center crashed with SIGSEGV in refresh_ui()
tags: removed: need-amd64-retrace
tags: added: running-unity
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Michael Terry (mterry)
visibility: private → public
Revision history for this message
Michael Terry (mterry) wrote :

This looks to be callbacks that aren't cleaned up when the panel dies. It looks like upstream's 3.6/3.8 update will fix most of these, as the refresh_ui call seems to be gone/obsolete there.

tags: added: precise
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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