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

Bug #978485 reported by Juan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

lost the driver of the card, and not connected by wireless, existing networks do not appear.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.0-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 2.0.1-0ubuntu1
Architecture: i386
Date: Tue Apr 10 19:15:11 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120224)
ProcCmdline: gnome-control-center network
ProcEnviron:
 LANGUAGE=es_CR:es
 PATH=(custom, no user)
 LANG=es_CR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb15e4659: mov 0x20(%esi),%ecx
 PC (0xb15e4659) ok
 source "0x20(%esi)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libnetwork.so
 g_cclosure_marshal_VOID__VOIDv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: [network]: gnome-control-center crashed with SIGSEGV in g_cclosure_marshal_VOID__VOIDv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu2
 deja-dup 22.0-0ubuntu1
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu1

Revision history for this message
Juan (eliasgenius) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #970115, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.