GNOME Bugzilla – Bug 680625
Wireless authentication doesn't continue automatically
Last modified: 2020-11-14 20:44:23 UTC
When turning on wireless radio at home, NetworkManager will automatically try to connect to my home network. This works fine, but often doesn't connect. When I click on the network manager icon, I see "authentication required". The password is already correctly saved, and no password dialog pops up. Doing a service NetworkManager restart, or (sometimes) turning off/on the radio will cause the password dialog to come up. When it does, simply clicking connect will work, as the box is already filled in with the correct password. You should never have to see the dialog unless the password is wrong. If NetworkManager really thinks the password is wrong initially (a different bug) and displays "authentication required" under the icon, it should definitely prompt you to give you a chance to click "try again". I am using FC17 with gnome3 and gnome shell. I am marking this as high because it's very difficult to connect to wireless. This happens on many different known networks. Thank you for your help!
So, would you give us some more details. * rpm -q NetworkManager * what type of Wi-Fi - WEP, WPA, EAP, ... and best attach /var/log/messages and if there is problem with associating/authenticating to AP, also /var/log/wpa_supplicant.log is of interest. For that see https://live.gnome.org/NetworkManager/Debugging/#wifi Note: the unnecessary password dialog pop-ups are fixed in git and should appear in Fedora soon (in 0.9.6 release).
Created attachment 219718 [details] tail -n 500 /var/log/messages | magicgrep-relevant stuff
Relevant logs, this current event occured after wake from suspend: $ rpm -q NetworkManager NetworkManager-0.9.4.0-9.git20120521.fc17.x86_64 WPA2 personal network There were no timestamps in wpa_supplicant.log so this is a long tail. Whether it coincides with the event or not, I cannot say: wlan0: Trying to associate with 00:18:39:c1:9c:a6 (SSID='octopus' freq=2447 MHz) wlan0: Associated with 00:18:39:c1:9c:a6 wlan0: WPA: Key negotiation completed with 00:18:39:c1:9c:a6 [PTK=CCMP GTK=CCMP] wlan0: CTRL-EVENT-CONNECTED - Connection to 00:18:39:c1:9c:a6 completed (auth) [id=0 id_str=] rfkill: WLAN hard blocked rfkill: WLAN hard blocked wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=4 wlan0: Failed to initiate AP scan wlan0: SME: Trying to authenticate with 00:18:39:c1:9c:a6 (SSID='octopus' freq=2447 MHz) wlan0: Trying to associate with 00:18:39:c1:9c:a6 (SSID='octopus' freq=2447 MHz) wlan0: Associated with 00:18:39:c1:9c:a6 wlan0: WPA: Key negotiation completed with 00:18:39:c1:9c:a6 [PTK=CCMP GTK=CCMP] wlan0: CTRL-EVENT-CONNECTED - Connection to 00:18:39:c1:9c:a6 completed (auth) [id=0 id_str=] wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3 dmesg: [509138.115150] PM: resume of devices complete after 2879.323 msecs [509138.115253] PM: Finishing wakeup. [509138.115254] Restarting tasks ... done. [509138.129029] video LNXVIDEO:00: Restoring backlight state [509138.336861] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X [509138.437606] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X [509138.438785] ADDRCONF(NETDEV_UP): eth0: link is not ready [509138.443534] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S [509138.443730] iwlwifi 0000:02:00.0: Radio type=0x1-0x3-0x1 [509138.560734] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jiri/others: please let me know if you need more info. Thanks, James
It seems to me that your magicgrep-relevant stuff filtered too much. Could you run in a terminal: # tail -f /var/log/messages then activate a connection and attach the messages displayed on the terminal. Did you try e.g in fallback mode?
Hi, Sorry for my slow reply. Unfortunately there wasn't anything else remotely relevant in /var/log/messages How would I activate fallback mode? Thanks
Here's how to activate fallback mode: library.gnome.org/users/gnome-help/3.3/fallback-mode.html.en https://wiki.archlinux.org/index.php/GNOME#Enabling_fallback_mode We need unfiltered /var/log/messages logs to see what happens. What NM version do you use?
yum info NetworkManager Installed Packages Name : NetworkManager Arch : x86_64 Epoch : 1 Version : 0.9.4.0 Release : 9.git20120521.fc17 Size : 6.8 M Repo : installed I've attached the tail of /var/log/messages since I woke my laptop from standby. I removed the 'info' lines that included public ip's. I also sensored the domain names. HTH, James
Created attachment 222645 [details] mildly sensored /var/log/messages since resume today
Ping? This still happens and is very annoying. On resume from suspend, sometimes it won't even prompt you at all, and is stuck on "authentication required". Eventually after several minutes, it will reprompt you. Why are you *ever* even prompted for the password, when it's correctly saved in the keyring!! NO change in Fedora 18.
*** Bug 689945 has been marked as a duplicate of this bug. ***
*** Bug 597889 has been marked as a duplicate of this bug. ***
Why is this still marked as new with 2 duplicates attached, and several people adding info?
*** Bug 784782 has been marked as a duplicate of this bug. ***
*** Bug 784784 has been marked as a duplicate of this bug. ***
Could anyone experiencing this problem please: nmcli g log level trace wait until the issue happens again, and then grab logs? If you're using the systemd journal, all you need is "journalctl -b -u NetworkManager". If you're not, then grab the /var/log/daemon.log or /var/log/NetworkManager.log or other logfile where NM log output goes. The existing dumps don't have enough information to say why NM is asking for the key again and not getting it.
I got 2 disconnects which I had to manually reconnect (first manual reconnect failed, second succeeded on both times) - But there was no password dialog box showing this time... On all previous disconnects I did get the password dialog box. Here's a shortened log, in case you're interested - let me know if I should open a new bug for that: https://ufile.io/ceiqh (available for 30 days) I've added (*** Here I manually selected to connect again ***) for the second manual reconnect (second time for the second disconnect).
Another disconnect which I had to manually reconnect twice (first time unsuccessfully tries for a while, second time succeeds almost instantly) https://pastebin.com/mJire2gX
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).