I encountered this bug in Gutsy Gibbon. When I just boot my notebook, I often see the following happen:
* 1.) Trying to connect to WLAN, but then I'm being asked for the WPA Key, although this key is already stored in the key chain. In the logfile, I see the following: .... Dec 16 11:29:09 jens-laptop NetworkManager: <info> Activation (eth1/wireless): access point 'DSLWLANXQRZ' is encrypted, and a key exists. No new key needed. .... Dec 16 11:29:36 jens-laptop NetworkManager: <info> Activation (eth1/wireless): disconnected during association, asking for new key. Dec 16 11:29:36 jens-laptop NetworkManager: <info> Activation (eth1) New wireless user key requested for network 'DSLWLANXQRZ'. .... * 2.) I cancel the dialog asking me for a new key. ... Dec 16 11:30:26 jens-laptop NetworkManager: <info> Activation (eth1) New wireless user key request for network 'DSLWLANXQRZ' was canceled. ... * 3.) I try again to connect to the network. For some milliseconds I think it is now working, but then again I am disconnected. For some reason NetworkManager thinks the connection is no longer valid??? .... Dec 16 11:30:29 jens-laptop NetworkManager: <info> Activation (eth1/wireless): access point 'DSLWLANXQRZ' is encrypted, and a key exists. No new key needed. ... Dec 16 11:30:50 jens-laptop NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'DSLWLANXQRZ'. .... Dec 16 11:31:07 jens-laptop NetworkManager: <info> Activation (eth1) successful, device activated. Dec 16 11:31:07 jens-laptop NetworkManager: <debug> [1197801067.245940] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'DSLWLANXQRZ' Dec 16 11:31:07 jens-laptop NetworkManager: <info> SWITCH: terminating current connection 'eth1' because it's no longer valid. Dec 16 11:31:07 jens-laptop NetworkManager: <info> Deactivating device eth1. Dec 16 11:31:08 jens-laptop NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed Dec 16 11:31:08 jens-laptop NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed * 4.) Again I force the NetworkManager to connect to my WLAN, and now everything works fine. Network Manager is using the following driver on my notebook. Dec 16 11:28:38 jens-laptop NetworkManager: <info> eth1: Device is fully-supported using driver 'ipw3945'. Find attached the complete log of NetworkManager. ** Attachment added: "Network Manager extract from syslog" http://launchpadlibrarian.net/10923976/networkmanager.syslog -- NM sometimes drops connection before associating, logfile says assertion `dev != NULL' failed https://bugs.launchpad.net/bugs/124706 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
