After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 697010 - NM keep asking wireless password, despite it is already provided by gnome-keyring.
NM keep asking wireless password, despite it is already provided by gnome-key...
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
0.9.8
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-03-31 23:42 UTC by gmRUQ7I8
Modified: 2014-10-13 12:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
/var/log/syslog (17.36 KB, text/x-log)
2013-04-16 14:41 UTC, gmRUQ7I8
Details

Description gmRUQ7I8 2013-03-31 23:42:40 UTC
Current behavior:
Each wifi connection is initialized, network manager shows password dialog, which is filed with password.

Expected behavior:
NM must silently read the saved password from the gnome-keyring and keep trying to connect forever using this password and never fail.
 
Unfortunately, when 'Available for all users' is checked, password is stored in /etc/... as plain-text, which is totally insecure, so this is not an option. Besides, it fails to soon. I mean, it has hard-coded only 3 authentication attempts, after which it clears the password and asks for new one and this is very annoying. The only case network-manager can show the password window, is the case when password is unavailable in gnome-keyring for specific ESSID. Once the password is saved in keyring, password window must never appear again for the same ESSID. Automatic password clearance procedure must be eliminated.
Comment 1 Dan Williams 2013-04-03 13:29:32 UTC
What version of NetworkManager do you have?  NM 0.9.8 reduced the frequency of wifi password requests.  With 0.9.8, NM will only ask for a password when it's 95% sure that the password is incorrect, or when WPA Enterprise authentication fails.
Comment 2 gmRUQ7I8 2013-04-07 06:22:23 UTC
I was using 0.9.4, when I raise an issue. As you recommended, I get updated to 0.9.8, using this https://bugzilla.redhat.com/show_bug.cgi?id=490493#c9 modification (I cannot get WIFI working other way). But problem has not gone away. Still, after reboot or suspend, NM does not instantiated connection immediately (ON/OFF button is replaced with 'Authentication required' message). But when it starts connecting after a couple of minutes, it asks the password.
Comment 3 Dan Williams 2013-04-08 21:01:27 UTC
To prevent the scanning issue you reference from that RedHat bug, lock the connection to the BSSID of your access point in the connection editor, and NetworkManager will no longer periodically scan.

Can you attach your /var/log/messages file from a bootup where you experienced the problem so we can debug the issue?
Comment 4 gmRUQ7I8 2013-04-16 14:41:19 UTC
Created attachment 241646 [details]
/var/log/syslog

Please have a look at my syslog entries. Looks like specific settings of my dbus cause the problem. Anyway, I've got this issue at least two systems.
Comment 5 gmRUQ7I8 2013-05-17 12:34:32 UTC
Two important details, I've figured out recently:
1. The problem take place for any type of network interface that uses 802.1x authentication. Wired or wireless, doesn't matter. 
2. The problem take place only if connection is initialized second time. For example, if I just logged in, I'm not getting asked for credentials. But if I switch the interface off, and turning it back on, credentials dialog is shown, just as if my PC is resumed after suspend.
Comment 6 gmRUQ7I8 2013-06-16 15:57:18 UTC
Any updates? This issue is very annoying.