NetworkManager crashed with SIGSEGV in __strcmp_sse42()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Return from suspend and appears the crash.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.1.90-0ubuntu5.1
ProcVersionSign
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CRDA: Error: [Errno 2] No existe el archivo o el directorio
Date: Wed Jan 4 08:35:57 2012
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
default via 10.123.123.1 dev wlan0 proto static
10.123.123.0/24 dev wlan0 proto kernel scope link src 10.123.123.44 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
Keyfiles: Error: [Errno 2] No existe el archivo o el directorio
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x7ffd9bd26996 <__strcmp_
PC (0x7ffd9bd26996) ok
source "(%rdi)" (0xffffffff9400
destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
__strcmp_sse42 () at ../sysdeps/
dhclient_start (client=<optimized out>, mode_opt=0x4ad3da "-S", release=0) at nm-dhcp-
nm_dhcp_
client_start (self=0x2541320, iface=<optimized out>, uuid=<optimized out>, ipv6=1, s_ip4=0x0, s_ip6=0x2542500, timeout=0, dhcp_anycast_
nm_dhcp_
Title: NetworkManager crashed with SIGSEGV in __strcmp_sse42()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #864795, 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.