GNOME Bugzilla – Bug 690457
nmcli cannot connect to wifi network
Last modified: 2020-11-12 14:32:51 UTC
Using nmcli I get 3 diffent messages, but I cannot connect to any wifi network: % nmcli con up id WIFI ** (process:28588): WARNING **: Could not initialize NMActiveConnection /org/freedesktop/NetworkManager/ActiveConnection/23: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (process:28588): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/23: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (process:28588): WARNING **: Could not create object for /org/freedesktop/NetworkManager/ActiveConnection/23: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist % nmcli con up id WIFI Error: Connection activation failed. % nmcli con up id WIFI ** (process:28619): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/26: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (process:28619): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/26: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist Error: Connection activation failed: Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/2' failed in libnm-glib. I'm using awesome as WM in KDE. I can connect to the WIFI network using the networkmanagement plasmoid. Ask if you need more informations. NM 0.9.6.4 Arch Linux
I can connect to LAN networks.
Still a problem with 0.9.8.0-1 ?
Yes, I get the same output with 0.9.8.0
NM bugzilla reorganization... sorry for the bug spam.
Do you still experience the problem? Could your NM installation be mangled somehow? Try to reinstall. Please provide output of these commands: $ nmcli -f name,devices,state,dbus-path c s $ nmcli c l $ nmcli dev wifi list Any errors in /var/log/messages.log ?
Still I can't connect with 0.9.8.8. $ nmcli -f name,devices,state,dbus-path c s NAME DEVICES STATE DBUS-PATH $ nmcli c l NAME UUID TYPE TIMESTAMP-REAL X 8abeec34-e760-42ad-861c-56ba0739a6ea 802-11-wireless Mon 10 Mar 2014 09:12:44 AM CET $ nmcli dev wifi list SSID BSSID MODE FREQ RATE SIGNAL SECURITY ACTIVE 'X' 00:C0:A8:E9:63:7A Infrastructure 2452 MHz 54 MB/s 67 WPA2 no
Created attachment 271399 [details] journal log
I don't see the manual connection attempt in the logs. There is just an auto-activation try when NM starts, that fails due to missing secrets, which might be the problem. nmcli don't support handling secrets yet. So either you have to (a) have some applet running, that can provide NM with the password (e.g. nm-applet, NM plasma applet, ...), or (b) have the password stored in the keyfile, so that NM don't need to ask for that. Mar 10 09:13:56 stockholm NetworkManager[211]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7] Could you run in one terminal (to get logs) $ sudo journalctl -fu NetworkManager and try to connect in another terminal with $ nmcli con up "X" If the missing password is the issue, you can add it to /etc/NetworkManager/system-connections/X, section [802-11-wireless-security] psk=your_password and make sure there is no 'psk-flags' there (or set it to 0: 'psk-flags=0')
Is exactly as you said. Replacing psk-flags=1 with psk=password fixed it. So, not a bug I guess :-)
We got a report recently downstream due to that same option being present in the config: https://bugs.gentoo.org/show_bug.cgi?id=528748 Not sure how that option is ending at in configs but, maybe NM should handle it a bit more gracefully as looks like it's a bit common to have it present
Also, is psk-flags=1 really valid or not? :/, maybe this is a duplicate of a nmcli bug that doesn't handle that option and forces people to store the passwords in the config file :| Thanks
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).