network-manager 0.6.6~rc2-0ubuntu1 wireless doesn't connect

[Matt Drake]

I just upgraded network-manager to version 0.6.6~rc2-0ubuntu1 in the hardy repositories, and now I can't connect to wireless networks.

Here's the output from syslog when I try to do so:

Mar 5 18:46:28 Old-Man-Jenkins dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Mar 5 18:46:28 Old-Man-Jenkins NetworkManager: <debug> [1204771588.096115] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'QUAD'
Mar 5 18:46:28 Old-Man-Jenkins NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / QUAD
Mar 5 18:46:28 Old-Man-Jenkins NetworkManager: <info> Deactivating device wlan0.
Mar 5 18:46:28 Old-Man-Jenkins NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Mar 5 18:46:28 Old-Man-Jenkins NetworkManager: <info> Device wlan0 activation scheduled...
Mar 5 18:46:28 Old-Man-Jenkins NetworkManager: <info> Deactivating device eth0.
Mar 5 18:46:28 Old-Man-Jenkins dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 8821
Mar 5 18:46:28 Old-Man-Jenkins dhclient: killed old client process, removed PID file
Mar 5 18:46:28 Old-Man-Jenkins dhclient: DHCPRELEASE on eth0 to 128.114.142.18 port 67
Mar 5 18:46:28 Old-Man-Jenkins avahi-daemon[5210]: Withdrawing address record for 169.233.5.107 on eth0.
Mar 5 18:46:28 Old-Man-Jenkins avahi-daemon[5210]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.233.5.107.
Mar 5 18:46:28 Old-Man-Jenkins avahi-daemon[5210]: Interface eth0.IPv4 no longer relevant for mDNS.
Mar 5 18:46:29 Old-Man-Jenkins avahi-daemon[5210]: Withdrawing address record for fe80::215:c5ff:fe6d:ef74 on eth0.
Mar 5 18:46:29 Old-Man-Jenkins avahi-daemon[5210]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::215:c5ff:fe6d:ef74.
Mar 5 18:46:29 Old-Man-Jenkins avahi-daemon[5210]: Interface eth0.IPv6 no longer relevant for mDNS.
Mar 5 18:46:29 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) started...
Mar 5 18:46:29 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 5 18:46:29 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 5 18:46:29 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 5 18:46:29 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 5 18:46:29 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 5 18:46:29 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0/wireless): access point 'QUAD' is unencrypted, no key needed.
Mar 5 18:46:30 Old-Man-Jenkins NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Mar 5 18:46:30 Old-Man-Jenkins NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant1886859122^I'
Mar 5 18:46:30 Old-Man-Jenkins NetworkManager: <info> SUP: response was 'OK'
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <info> Error opening control interface to supplicant.
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <WARN> real_act_stage2_config(): Activation (wlan0/wireless): couldn't connect to the supplicant.
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) failure scheduled...
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) failed for access point (QUAD)
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <info> Activation (wlan0) failed.
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <info> Deactivating device wlan0.
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <WARN> nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for device wlan0: Invalid argument
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
Mar 5 18:46:31 Old-Man-Jenkins NetworkManager: <info> Will activate connection 'eth0'.

It then goes on to activate eth0

[Caroline Ford (secretlondon)]

Network manager in hardy is currently broken. An updated source has been uploaded.

[danda (dan-osc)]

This is happening to me too. Is there a workaround, or instructions for downgrading network-manager to latest stable version?

[Vytas (vytas)]

First, can you check what is your current version?
Could you also comment on the main bug, not on the duplicate? thanks