NetworkManager crashes when I bring up the settings dialog from nm-applet

[Anna Glasgall]

Binary package hint: network-manager

NetworkManager crashes when I bring up the settings dialog from nm-applet. Furthermore, when NM goes down, it takes my wireless connection with it.

Steps to reproduce:

1) Right-click on nm-applet icon
2) Select "Edit Connections"
3) Observe NetworkManager crash and bring down wireless connectivity

I'm not convinced this is a duplicate of #432452; the stack trace shows that this crash is in libpolkit-dbus, whereas #432452's is in libgobject.

ProblemType: Crash
Architecture: amd64
Date: Sun Oct 4 01:07:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.100 metric 2
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.1.1 dev wlan0 proto static
Package: network-manager 0.8~a~git.20090923t064445.b20cef2-0ubuntu2
ProcCmdline: NetworkManager
ProcCwd: /
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x7f1da15cd531: mov (%rbx),%rbp
 PC (0x7f1da15cd531) ok
 source "(%rbx)" (0x00000002) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? () from /usr/lib/libpolkit-gobject-1.so.0
 ?? () from /usr/lib/libpolkit-gobject-1.so.0
 ?? ()
 ?? ()
 invoke_object_method (object=0x1785040,
Title: NetworkManager crashed with SIGSEGV in invoke_object_method()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups:

WpaSupplicantLog:

[Apport retracing service (apport)]

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.