NetworkManager crashed with SIGSEGV in _polkit_authority_check_authorization()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
Updated with aptitude update && aptitude safe-upgrade today september 25. 2009
Release:
Description: Ubuntu karmic (development branch)
Release: 9.10
---
network-manager:
Installed: 0.8~a~git.
Candidate: 0.8~a~git.
Version table:
*** 0.8~a~git.
500 http://
100 /var/lib/
---
ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
CrashCounter: 1
Date: Fri Sep 25 17:52:37 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
192.168.242.0/24 dev vmnet8 proto kernel scope link src 192.168.242.1
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.50 metric 2
172.16.169.0/24 dev vmnet1 proto kernel scope link src 172.16.169.1
169.254.0.0/16 dev wlan0 scope link metric 1000
default via 192.168.1.1 dev wlan0 proto static
NonfreeKernelMo
Package: network-manager 0.8~a~git.
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7f833bcac9f9 <_polkit_
PC (0x7f833bcac9f9) ok
source "%rax" ok
destination "0x0(%rbp)" (0x700000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
_polkit_
?? () from /usr/lib/
?? ()
?? ()
?? () from /usr/lib/
Title: NetworkManager crashed with SIGSEGV in _polkit_
Uname: Linux 2.6.31-10-generic x86_64
UserGroups:
WpaSupplicantLog:
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.