nm-applet crashed with SIGSEGV

[Max Bowsher]

Crash immediately after login. Probably a dupe. Reporting for the retracer to analyze.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-manager-gnome 0.8.4~git.20110228t141430.abba62f-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic i686
Architecture: i386
CrashCounter: 1
Date: Thu Mar 17 11:21:24 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 192.168.23.0/24 dev wlan0 proto kernel scope link src 192.168.23.246 metric 2
 default via 192.168.23.1 dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SegvAnalysis:
 Segfault happened at: 0xfa4c26: movsbl (%eax),%eax
 PC (0x00fa4c26) ok
 source "(%eax)" (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 2010-12-16 (90 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.