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

Bug #1054275 reported by Jacob Henner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Crashes when trying to adjust wifi network from within dialog

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu15
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Fri Sep 21 14:32:44 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4)
ProcCmdline: gnome-control-center network connect-8021x-wifi /org/freedesktop/NetworkManager/Devices/0 /org/freedesktop/NetworkManager/AccessPoint/0
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f91b756afc5: mov 0x10(%rax),%rdi
 PC (0x7f91b756afc5) ok
 source "0x10(%rax)" (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
 ?? () 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
Title: [network]: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to quantal on 2012-09-19 (1 days ago)
UserGroups: adm cdrom debian-tor dip lpadmin netdev plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 23.92-0ubuntu1
 gnome-control-center-signon 0.0.17-0ubuntu1
 indicator-datetime 12.10.1-0ubuntu1

Revision history for this message
Jacob Henner (jacobhenner) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 get_selected_object (panel=panel@entry=0x7f91e3902620) at cc-network-panel.c:326
 wimax_enabled_toggled (client=0x7f91e3b94a10, pspec=<optimized out>, panel=0x7f91e3902620) at cc-network-panel.c:1438
 g_closure_invoke (closure=0x7f91e3f57820, return_value=0x0, n_param_values=2, param_values=0x7fffee293680, invocation_hint=0x7fffee293620) at /build/buildd/glib2.0-2.33.14/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x7f91e38c5da0, detail=detail@entry=2036, instance=instance@entry=0x7f91e3b94a10, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffee293680) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3551
 g_signal_emit_valist (instance=0x7f91e3b94a10, signal_id=<optimized out>, detail=2036, var_args=var_args@entry=0x7fffee2938d8) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3300

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_closure_invoke()
+ get_selected_object()
tags: removed: need-amd64-retrace
information type: Private → Public
Changed in gnome-control-center (Ubuntu):
importance: Medium → Low
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: New → 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.