NetworkManager crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
I have no notice of network configuration problem, I just clicked on crash report, I do not know why and what happened ..
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 16 14:23:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/
IpRoute:
192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.99 metric 2
192.168.0.0/24 dev wlan1 proto kernel scope link src 192.168.0.127
169.254.0.0/16 dev wlan1 scope link metric 1000
default via 192.168.1.1 dev wlan1 proto static
NonfreeKernelMo
Package: network-manager 0.8~a~git.
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7ff18eee3531: movl $0x4e81824,
PC (0x7ff18eee3531) ok
source "$0x4e81824" ok
destination "0x4c(%rcx,%rcx,4)" (0x01673d4c) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? ()
?? ()
?? () from /usr/lib/
Title: NetworkManager crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:
WpaSupplicantLog:
visibility: | private → public |
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 #430044, 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.