NetworkManager crashed with SIGSEGV

Bug #455273 reported by Daniele Cruciani
10
This bug affects 1 person
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/NetworkManager
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
NonfreeKernelModules: nvidia
Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7ff18eee3531: movl $0x4e81824,0x4c(%rcx,%rcx,4)
 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/libpolkit-gobject-1.so.0
 ?? () from /usr/lib/libpolkit-gobject-1.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: NetworkManager crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

WpaSupplicantLog:

Revision history for this message
Daniele Cruciani (daniele-smartango) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.