NetworkManager crashed with SIGSEGV in g_type_instance_get_private()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Tried enabling the IPv6 "automatic" connection type. My ISP doesn't provide IPv6 connectivity, nor is my router set up for IPv6, I wanted to see if Ubuntu would find a teredo tunnel to use. I expected a failure message, but instead network-manager crashed.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.8.9997+
ProcVersionSign
Uname: Linux 3.0.0-5-generic x86_64
NonfreeKernelMo
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Sun Jul 17 10:18:31 2011
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
IpRoute:
default via 192.168.0.1 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.102 metric 1
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:
SegvAnalysis:
Segfault happened at: 0x7fa288a0a731 <g_type_
PC (0x7fa288a0a731) ok
source "$0x0" ok
destination "(%rdi)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
g_type_
nm_agent_
?? ()
?? ()
?? ()
Title: NetworkManager crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to oneiric on 2011-07-17 (0 days ago)
UserGroups:
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.