802.1X fails with assertions

[Jtb]

Binary package hint: network-manager

After bug #426692 has been fixed I'm trying to establish a 802.1X connection.
But every attempt fails with the following messages:

Sep 16 12:13:33 ws-jweibler NetworkManager: <info> Activation (eth0) starting connection '802.1x'
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0)
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0)
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> Activation (eth0/wired): connection '802.1x' has security, but secrets are required.
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> (eth0): device state change: 5 -> 6 (reason 0)
Sep 16 12:13:33 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Sep 16 12:13:36 ws-jweibler NetworkManager: <WARN> secrets_update_setting(): Failed to update connection secrets: 1 ipv4
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> (eth0): device state change: 6 -> 4 (reason 0)
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0)
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Activation (eth0/wired): connection '802.1x' requires no security. No secrets needed.
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> (eth0): supplicant interface state: starting -> ready
Sep 16 12:13:36 ws-jweibler NetworkManager: dbus_g_proxy_get_path: assertion `DBUS_IS_G_PROXY (proxy)' failed
Sep 16 12:13:36 ws-jweibler NetworkManager: nm_supplicant_config_add_setting_8021x: assertion `connection_uid != NULL' failed
Sep 16 12:13:36 ws-jweibler NetworkManager: <WARN> build_supplicant_config(): Couldn't add 802.1X security setting to supplicant config.
Sep 16 12:13:36 ws-jweibler NetworkManager: <WARN> supplicant_iface_state_cb_handler(): Activation (eth0/wired): couldn't build security configuration.
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> (eth0): device state change: 5 -> 9 (reason 9)
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Marking connection '802.1x' invalid.
Sep 16 12:13:36 ws-jweibler NetworkManager: <info> Activation (eth0) failed.

Description: Ubuntu karmic (development branch)
Release: 9.10

network-manager:
  Installed: 0.8~a~git.20090911t130220.4c77fa0-0ubuntu3
  Candidate: 0.8~a~git.20090911t130220.4c77fa0-0ubuntu3
  Version table:
 *** 0.8~a~git.20090911t130220.4c77fa0-0ubuntu3 0
        500 http://ftp.fbihome.de karmic/main Packages
        100 /var/lib/dpkg/status

plasma-widget-networkmanagement:
  Installed: 0.1~svn1023224-0ubuntu1
  Candidate: 0.1~svn1023224-0ubuntu1
  Version table:
 *** 0.1~svn1023224-0ubuntu1 0
        500 http://ftp.fbihome.de karmic/main Packages
        100 /var/lib/dpkg/status

[zdenek smetana (zyghom)]

I have same problem with NM although not only under Ubuntu
and the problem only exists for WPA2-PSK, it is working fine for WEP

[Rami Al-Rfou' (rmyeid)]

Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 9.10
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 10.144.180.0/23 dev eth0 proto kernel scope link src 10.144.180.10
 default via 10.144.180.1 dev eth0
Package: network-manager 0.8~a~git.20090923t064445.b20cef2-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Rami Al-Rfou' (rmyeid)]

The problem as follows:
1- I make a new connection with 802.1x security/Tunneled TLS and fill the authentication options
2- try to use the new connection to connect it does not work with these messages from syslog
   Sep 29 01:03:55 aboSamoor NetworkManager: dbus_g_proxy_get_path: assertion `DBUS_IS_G_PROXY (proxy)' failed
   Sep 29 01:03:55 aboSamoor NetworkManager: nm_supplicant_config_add_setting_8021x: assertion `connection_uid != NULL' failed
   Sep 29 01:03:55 aboSamoor NetworkManager: <WARN> build_supplicant_config(): Couldn't add 802.1X security setting to supplicant config.
   Sep 29 01:03:55 aboSamoor NetworkManager: <WARN> supplicant_iface_state_cb_handler(): Activation (eth0/wired): couldn't build security configuration.
   Sep 29 01:03:55 aboSamoor NetworkManager: <info> (eth0): device state change: 5 -> 9 (reason 9)
3- No internet
4- Write manually a wpa_supplicant.conf file
5-run sudo wpa_supplicant -i eth0 -c /etc/wpa_supplicant.conf -D wired -B && sudo dhclient eth0
6- I have internet connection :)

[Alexander Sack (asac)]

please try this patch.

some instructions how to try a patch are here: https://wiki.ubuntu.com/DebuggingNetworkManager#Testing%20a%20patch

[Rami Al-Rfou' (rmyeid)]

I applied the patch, and it seems working without any intervention. Should I remove the /etc/wpa_supplicant.conf because it was not there when the nm was working before ? I attached what I thought the important part of the syslog.

[Alexander Sack (asac)]

dupe of bug 430551