nm-applet crashed with SIGABRT in __kernel_vsyscall()

[Péter Trombitás]

I was booting from the precise daily build i386 iso downloaded on 12th January 2012.
This issue happened when I tried to connect to a secured wi-fi network while running the installation session. Then a GTK window told me that some error encountered and a desktop session was started. I tried to start nm-applet from ALT+F2, it showed up in the notification are and crashed.
Here's the ouput in terminal:
ubuntu@ubuntu:~$ nm-applet
** Message: applet now removed from the notification area
** Message: No keyring secrets found for SMC/802-11-wireless-security; asking user.
**
ERROR:nm-utils.c:1231:nm_utils_security_valid: assertion failed: (have_ap)
Aborted (core dumped)

these might be useful too:
ubuntu@ubuntu:~$ iwconfig
lo no wireless extensions.

eth1 IEEE 802.11abg ESSID:"g\xC6isQ\xFFJ\xEC)\xCD\xBA\xAB\xF2\xFB\xE3F|\xC2T\xF8\x1B\xE8\xE7\x8DvZ.c3\x9F\xC9\x9A"
          Mode:Managed Channel:0 Access Point: Not-Associated
          Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
          Retry limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.
ubuntu@ubuntu:~$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

If this is a useful info, I have an Intel PRO/Wireless chipset that needed the ipw2200 firmware in a Debian installation.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-manager-gnome 0.9.1.90-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0
Uname: Linux 3.2.0-8-generic-pae i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CasperVersion: 1.297
Date: Sat Jan 14 20:23:56 2012
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.2.1 dev eth0 proto static
 169.254.0.0/16 dev eth0 scope link metric 1000
 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.101 metric 1
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120112)
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile

 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: network-manager-applet
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nm-applet crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 SMC 4807b5cc-4bd6-463a-87c3-275bb02b62e9 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/1
 Wired connection 1 7d5c5000-591b-47e8-aa9e-0d2f2e2d4efa 802-3-ethernet 1326572658 Sat 14 Jan 2012 08:24:18 PM UTC yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
 eth1 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.3.0 connected enabled enabled enabled enabled disabled

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #908380, 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.