[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/269891 Title: WPA supplicant cannot scan for AP's after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
Same problem here with Maverick and Intel 5300 AGN, no association after suspend, but everything works after reboot. This repeats several times while trying associate: Nov 21 22:37:07 wpa_supplicant[924]: Trying to associate with 00:24:fe:a6:35:f2 (SSID='bluebox' freq=2412 MHz) Nov 21 22:37:07 NetworkManager[780]: (wlan1): supplicant connection state: disconnected -> associating Nov 21 22:37:07 wpa_supplicant[924]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Nov 21 22:37:07 NetworkManager[780]: (wlan1): supplicant connection state: associating -> disconnected Nov 21 22:37:17 wpa_supplicant[924]: Authentication with 00:00:00:00:00:00 timed out. Nov 21 22:37:17 wpa_supplicant[924]: Failed to initiate AP scan. Btw i see the line "Failed to initiate AP scan." after a working connection too, so it may not be the indicator for the problem. -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
I have a problem with the same symptoms running Karmic on a Thinkpad X60 with Intel PRO/Wireless 3945ABG [Golan]: NetworkManager shows available networks only from boot to first suspend. It fails to list or connect to wlans afterwards. -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
I have the same issue, here is a workaround, do it manually: I think the issue is related to the network manager, disable its handling of the wireless connection. and then add to /etc/network/interfaces the following lines iface wlan0 inet dhcp wpa-ssid "YourNetworkSSID" wpa-psk YourNetworkPassword to connect/disconnect: sudo ifup wlan0 sudo ifdown wlan0 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
This seems to be the case for me, too. I have Jaunty 9.04 on a Asus EeePC 100H. The kernel is 2.6.30-generic, which has the driver for rt2860 version 1.8.1.1. I have no problem on statup: as soon as I get into my account, Network Manager is already getting the wi-fi working. If I suspend or hibernate the system, on resume Network Manager shows no wi-fi network, while `iwlist ra0 scan` does. Looking at daemon.log, it seems that it's waiting for wpasupplicant: --- Jul 2 02:04:32 lopo-netbook NetworkManager: Waking up... Jul 2 02:04:32 lopo-netbook NetworkManager: (eth0): now managed Jul 2 02:04:32 lopo-netbook NetworkManager: (eth0): device state change: 1 -> 2 Jul 2 02:04:32 lopo-netbook NetworkManager: (eth0): bringing up device. Jul 2 02:04:32 lopo-netbook NetworkManager: (eth0): preparing device. Jul 2 02:04:32 lopo-netbook NetworkManager: (eth0): deactivating device (reason: 2). Jul 2 02:04:32 lopo-netbook NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Jul 2 02:04:32 lopo-netbook NetworkManager: Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Jul 2 02:04:32 lopo-netbook NetworkManager: (ra0): now managed Jul 2 02:04:32 lopo-netbook NetworkManager: (ra0): device state change: 1 -> 2 Jul 2 02:04:32 lopo-netbook NetworkManager: (ra0): bringing up device. Jul 2 02:04:32 lopo-netbook NetworkManager: (ra0): preparing device. Jul 2 02:04:32 lopo-netbook NetworkManager: (ra0): deactivating device (reason: 2). Jul 2 02:04:32 lopo-netbook NetworkManager: (ra0): device state change: 2 -> 3 Jul 2 02:04:32 lopo-netbook NetworkManager: (ra0): supplicant interface state: starting -> ready --- After the last line, nothing happens for tens of minutes. I thought it was watiting for wpasupplicant, so I tried to `killall wpa_supplicant`: - Jul 2 02:05:20 lopo-netbook NetworkManager: (ra0): supplicant manager state: idle -> down Jul 2 02:05:20 lopo-netbook NetworkManager: (ra0): device state change: 3 -> 2 Jul 2 02:05:20 lopo-netbook NetworkManager: (ra0): deactivating device (reason: 10). Jul 2 02:05:20 lopo-netbook NetworkManager: nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device ra0: Network is down Jul 2 02:05:20 lopo-netbook NetworkManager: nm_device_wifi_disable_encryption(): error setting key for device ra0: Network is down Jul 2 02:05:20 lopo-netbook NetworkManager: nm_device_wifi_set_mode(): error setting card ra0 to mode 2: Network is down Jul 2 02:05:20 lopo-netbook NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed Jul 2 02:05:20 lopo-netbook NetworkManager: Trying to start the supplicant... Jul 2 02:05:20 lopo-netbook NetworkManager: (ra0): supplicant manager state: down -> idle Jul 2 02:05:20 lopo-netbook NetworkManager: (ra0): device state change: 2 -> 3 Jul 2 02:05:21 lopo-netbook NetworkManager: (ra0): supplicant interface state: starting -> ready -- Once again, no network list (and no associating) in Network Manager. I tried to kill wpa_supplicant again, and now my wi-fi SSID showed in the list, NM tried to associate with it, but without success: -- Jul 2 02:06:21 lopo-netbook NetworkManager: (ra0): supplicant manager state: idle -> down Jul 2 02:06:21 lopo-netbook NetworkManager: (ra0): device state change: 3 -> 2 Jul 2 02:06:21 lopo-netbook NetworkManager: (ra0): deactivating device (reason: 10). Jul 2 02:06:21 lopo-netbook NetworkManager: nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device ra0: Network is down Jul 2 02:06:21 lopo-netbook NetworkManager: nm_device_wifi_disable_encryption(): error setting key for device ra0: Network is down Jul 2 02:06:21 lopo-netbook NetworkManager: nm_device_wifi_set_mode(): error setting card ra0 to mode 2: Network is down Jul 2 02:06:21 lopo-netbook NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed Jul 2 02:06:21 lopo-netbook NetworkManager: Trying to start the supplicant... Jul 2 02:06:21 lopo-netbook NetworkManager: (ra0): supplicant manager state: down -> idle Jul 2 02:06:21 lopo-netbook NetworkManager: (ra0): device state change: 2 -> 3 Jul 2 02:06:22 lopo-netbook NetworkManager: (ra0): supplicant interface state: starting -> ready Jul 2 02:06:27 lopo-netbook NetworkManager: Activation (ra0) starting connection 'Auto Alice-43549390' Jul 2 02:06:27 lopo-netbook NetworkManager: (ra0): device state change: 3 -> 4 Jul 2 02:06:27 lopo-netbook NetworkManager: Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled... Jul 2 02:06:27 lopo-netbook NetworkManager:
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
Hi maleadt, Sorry for the extremely delayed response here. Can you comment if this is still an issue with the latest pre-release of Jaunty 9.04, currently the Beta release - http://www.ubuntu.com/testing/jaunty/beta . You should be able to test via a LiveCD. Please let us know your results. Thanks. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Tags added: intrepid ** Tags added: resume -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
this perfectly works on other chipsets, so this is very likely a driver/kernel issue. As I don't have enough ralink RT25xx driver knowledge, I'm reassigning this bug to linux in the hope that they can triage this bug with more insight than me. ** Changed in: linux (Ubuntu) Sourcepackagename: wpasupplicant => linux -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Attachment added: "dmesg-suspended.log.bz2" http://launchpadlibrarian.net/17595297/dmesg-suspended.log.bz2 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Attachment added: "wpasupplicant_log.tar.bz2" http://launchpadlibrarian.net/17595249/wpasupplicant_log.tar.bz2 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Attachment added: "networkmanager_log.tar.bz2" http://launchpadlibrarian.net/17595246/networkmanager_log.tar.bz2 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Attachment added: "pm-suspend.log.bz2" http://launchpadlibrarian.net/17595238/pm-suspend.log.bz2 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Attachment added: "system_log.tar.bz2" http://launchpadlibrarian.net/17595226/system_log.tar.bz2 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Attachment added: "lspci.log.bz2" http://launchpadlibrarian.net/17595218/lspci.log.bz2 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Attachment added: "kernel_log.tar.bz2" http://launchpadlibrarian.net/17595209/kernel_log.tar.bz2 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
[Bug 269891] Re: WPA supplicant cannot scan for AP's after suspend
** Attachment added: "dmesg-normal_log.bz2" http://launchpadlibrarian.net/17595206/dmesg-normal_log.bz2 -- WPA supplicant cannot scan for AP's after suspend https://bugs.launchpad.net/bugs/269891 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
