NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()

Bug #437005 reported by James Dearing
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

No idea when this happened or whether it's repeatable; I just looked in my system tray and there was this "Crash report detected" icon.

ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Fri Sep 25 18:19:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.4 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 10.0.1.1 dev wlan0 proto static
NonfreeKernelModules: nvidia
Package: network-manager 0.8~a~git.20090923t064445.b20cef2-0ubuntu1
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SegvAnalysis:
 Segfault happened at: 0x7f8c76039e96 <nm_settings_connection_interface_emit_updated+38>: cmpq $0x0,0x28(%rax)
 PC (0x7f8c76039e96) ok
 source "$0x0" ok
 destination "0x28(%rax)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_settings_connection_interface_emit_updated ()
 ?? () from /usr/lib/libnm-glib.so.2
 ?? ()
 ?? ()
 ?? () from /usr/lib/libpolkit-gobject-1.so.0
Title: NetworkManager crashed with SIGSEGV in nm_settings_connection_interface_emit_updated()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups:

Revision history for this message
James Dearing (dearingj) wrote :
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 #435029, 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.

visibility: private → public
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.