nm-applet crashed with SIGSEGV directly after logging in

[Julian Schlichtholz]

After logging in just the background is shown while no HUD is loaded. Some seconds later the delivered message appeared.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-manager-gnome 0.8.4~git.20110228t141430.abba62f-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5
Uname: Linux 2.6.38-4-generic i686
Architecture: i386
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Date: Thu Mar 17 12:09:50 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nm-applet
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
IpRoute:
 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.25 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.178.1 dev eth0 proto static
Keyfiles: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RfKill:

SegvAnalysis:
 Segfault happened at: 0x211c26: movsbl (%eax),%eax
 PC (0x00211c26) 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 2011-02-23 (21 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1681): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[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.