On 18/08/17 03:19 PM, Bengt Gördén wrote:
The problem is not with setting up the connection, but with trying to
use it. I can see the SSID. When I try to connect to it and enter the password, it won't authenticate. To keep things simple, I used xxxxxxxx as the password. (Don't tell anyone. It's secret. <g>). At this point, the WPA2 password should be accepted and the connection allowed to proceed, as it would with any other access point. It doesn't.
Just a thought. Policykit might be involved
Check with:
journalctl -u polkit.service --since "24 hour ago"
# journalctl -u polkit.service --since "24 hour ago" -- Logs begin at Fri 2017-08-18 10:03:22 EDT, end at Fri 2017-08-18 15:22:46 EDT. -- Aug 18 10:03:38 E520 systemd[1]: Starting Authorization Manager... Aug 18 10:03:38 E520 polkitd[1098]: Started polkitd version 0.113 Aug 18 10:03:38 E520 polkitd[1098]: Loading rules from directory /etc/polkit-1/rules.d Aug 18 10:03:38 E520 polkitd[1098]: Loading rules from directory /usr/share/polkit-1/rules.d Aug 18 10:03:38 E520 polkitd[1098]: Finished loading, compiling and executing 3 rules Aug 18 10:03:38 E520 systemd[1]: Started Authorization Manager. Aug 18 10:03:38 E520 polkitd[1098]: Acquired the name org.freedesktop.PolicyKit1 on the system bus Aug 18 10:04:15 E520.jknott.net polkitd[1098]: Registered Authentication Agent for unix-session:1 (system bus name :1.27 [/usr Aug 18 10:07:38 E520.jknott.net polkitd[1098]: Operator of unix-session:1 successfully authenticated as unix-user:root to gain lines 1-10/10 (END) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org