nm-applet crashes after entering password for 802.1x network

[Krystl]

I'm connected to 802.1x protected network, when I unplug the cable and plug it in again, network manager asks me for password. After entering the password network manager applet crashes with following error:

ERROR:eap-method-peap.c:128:fill_connection: assertion failed: (s_con)

9.04 didn't asks me, and if so the password was prefilled.

apt-cache policy network-manager-gnome
network-manager-gnome:
  Installed: 0.8~a~git.20091014t134532.4033e62-0ubuntu1
  Candidate: 0.8~a~git.20091014t134532.4033e62-0ubuntu1
  Version table:
 *** 0.8~a~git.20091014t134532.4033e62-0ubuntu1 0
        500 http://cz.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Nov 10 14:13:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nm-applet
IpRoute:
 10.160.11.0/24 dev eth0 proto kernel scope link src 10.160.11.112 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 10.160.11.1 dev eth0 proto static
NonfreeKernelModules: nvidia wl
Package: network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-15.49-generic
SourcePackage: network-manager-applet
Uname: Linux 2.6.31-15-generic i686
WpaSupplicantLog:

XsessionErrors:
 (gnome-settings-daemon:1884): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1884): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1925): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1908): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:1904): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[Seva Gluschenko (gvs-ya)]

This bug affects me, too: when I'm trying to connect to 802-1x wired network, the network-manager-applet asks for the private key (despite it's entered already) and its passphrase. After entering the passphrase the applet crashes with the similar error:

ERROR:eap-method-tls.c:134:fill_connection: assertion failed: (s_con)

Upon initialization NetworkManager reported the following error:

NetworkManager: crypto_get_private_key_data: assertion `password != NULL' failed

Hope it helps.

apt-cache policy network-manager-gnome
network-manager-gnome:
  Installed: 0.8~rc2-0ubuntu2~nmt2~karmic
  Candidate: 0.8~rc2-0ubuntu2~nmt2~karmic
  Version table:
 *** 0.8~rc2-0ubuntu2~nmt2~karmic 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     0.8~a~git.20091014t134532.4033e62-0ubuntu1 0
        500 http://ru.archive.ubuntu.com karmic/main Packages

[dogganos (gpall)]

Me too... I can't even connect to the 802.1x network. It does not accept any setting that I set.
And why, BTW, in the 802.1x tab you have to fill so many fields (PEAP version, anonymous identity), when in MS Windoze it just plays without those? Anyway, just asking, not whining!

# apt-cache policy network-manager-gnome
network-manager-gnome:
  Installed: 0.8~a~git.20091014t134532.4033e62-0ubuntu1
  Candidate: 0.8~a~git.20091014t134532.4033e62-0ubuntu1
  Version table:
 *** 0.8~a~git.20091014t134532.4033e62-0ubuntu1 0
        500 http://gr.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

[Krystl (xkrystl)]

Nm-applet still crashing, but connection to 802.1x is possible. Here is my solution: when dialog appears to enter password, you can enter anything, doesn't matter, because nm-applet crashes right after you click connect. Then open console and run nm-applet &. The you can choose again 802.1x protected network to connect. Now it's working OK. So doesn't matter what password you enter to dialog, the important is to enter right password in Edit Connection dialog.

[[e-mail] (thedyynz)]

Wasn't there the exact same bug a year or so ago? I remember having the exact same problem, and it's still not fixed (or broken) again. I had to resort to the exact same thing as krystl says. This happens in Lucid.