NetworkManager crashed with SIGSEGV in g_type_instance_get_private()

Bug #852257 reported by Rodrigo Hernandes
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

modifying the DNS address, putting the number of OpenDNS

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CRDA: Error: [Errno 2] Arquivo ou diretório não encontrado
Date: Fri Sep 16 20:24:50 2011
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901)
IpRoute:
 default via 189.54.192.1 dev eth0 proto static
 169.254.0.0/16 dev eth0 scope link metric 1000
 189.54.192.0/21 dev eth0 proto kernel scope link src 189.54.199.59
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] Arquivo ou diretório não encontrado
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
PciNetwork:

ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:

SegvAnalysis:
 Segfault happened at: 0x7f29469f7b41 <g_type_instance_get_private+33>: cmpq $0x0,(%rdi)
 PC (0x7f29469f7b41) ok
 source "$0x0" ok
 destination "(%rdi)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 g_type_instance_get_private () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 nm_agent_manager_save_secrets ()
 ?? ()
 ?? ()
 ?? ()
Title: NetworkManager crashed with SIGSEGV in g_type_instance_get_private()
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (0 days ago)
UserGroups:

mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-16T20:24:50.358195

Revision history for this message
Rodrigo Hernandes (ortegahernandes) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #797868, 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
tags: removed: need-amd64-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.