Public bug reported: 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 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: 802.1x dot1x ** Description changed: Binary package hint: network-manager - After bug #42669 has been fixed I'm trying to establish a 802.1X connection. + 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 -- 802.1X fails with assertions https://bugs.launchpad.net/bugs/430551 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs