nm-applet crashed with SIGSEGV

[Micah Gersten]

This crashed right after Bug #731087

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-manager-gnome 0.8.4~git.20110228t141430.abba62f-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
Date: Tue Mar 8 00:32:04 2011
ExecutablePath: /usr/bin/nm-applet
InterestingModules: ndiswrapper
IpRoute:
 192.168.15.0/24 dev wlan4 proto kernel scope link src 192.168.15.100 metric 2
 10.42.43.0/24 dev eth6 proto kernel scope link src 10.42.43.1 metric 1
 169.254.0.0/16 dev wlan4 scope link metric 1000
 default via 192.168.15.1 dev wlan4 proto static
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f406c2eccd0: movsbl (%rdi),%eax
 PC (0x7f406c2eccd0) ok
 source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: nm-applet crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-03-06 (1 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev sambashare sbuild vboxusers video
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 #729150, 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.