NetworkManager crashed with SIGSEGV in nm_dhcp_client_start_ip6()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 11.10 64bit
Laptop Aspire 4830TG-6450
Problem happens when opening laptop lid to resume from sleep -> entering password -> resuming desktop.
Network starts to resume but issues error about crashing, then after a few seconds it resumes as normal.
Also noticed network does not remember the last used network and tries connecting to neighbors sometimes.
I could just ignore this type of error but I though better handeling of the network after resuming connection would be a better choice.
Let me know if any more info is needed.
Thanks in advance.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.1.90-0ubuntu5.1
ProcVersionSign
Uname: Linux 3.0.0-20-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Thu Jun 7 12:40:28 2012
ExecutablePath: /usr/sbin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.107 metric 2
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SegvAnalysis:
Segfault happened at: 0x7f17e47d2726: movdqu (%rdi),%xmm1
PC (0x7f17e47d2726) ok
source "(%rdi)" (0xffffffffd400
destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
?? () from /lib/x86_
?? ()
nm_dhcp_
?? ()
nm_dhcp_
Title: NetworkManager crashed with SIGSEGV in nm_dhcp_
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.