You are not logged in.
Mb Late but for me this help
nmcli connection delete DIR-842
nmcli device wifi connect <SSID> password <PASSWORD>Offline
I've been experiencing this with either of the backends for the past few months, and lately the aforementioned "solution" of deleting the connection stopped working. I now occasionally get this same error even on the first connection attempt, after purging saved connections and even rebooting for a good measure.
edit:
Just had to reboot the laptop to connect to either of the two wifi networks in my house
Just in case, I'm using gnome-keyring.
Last edited by hjvt.dev (2025-04-11 22:30:12)
Offline
I suspect this is related to how NM stores the network key and whether something like kwallet or gnome-keyring is involved.
What DE do you use (or password/secret manager if there's a standalone one)?
Online
I've been experiencing this with either of the backends for the past few months, and lately the aforementioned "solution" of deleting the connection stopped working. I now occasionally get this same error even on the first connection attempt, after purging saved connections and even rebooting for a good measure.
edit:
Just had to reboot the laptop to connect to either of the two wifi networks in my house.
So, uh, the only reliable way to connect to wifi for me right now is to
1. nmcli connection delete $ssid
2. systemctl restart iwd
3. nmcli dewice wifi connect $ssid
Either of the first two steps on it's own is not helping.
Offline
You're not supposed to start iwd when using NM itfp.
Please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -fOnline
You're not supposed to start iwd when using NM itfp.
Please post the output offind /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
I don't start it, nor have it enabled. I presume NM itself starts it, since killing iwd and not restarting it renders NM `device wifi` commands inoperable.
Offline
Are you https://wiki.archlinux.org/title/Networ … Fi_backend ? (That'S not default)
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stafter connecting tho your wifi.
Online
also happened to me on arch after a recent update. deleting the connection in nmcli and reconnecting solved the issue for me
nmcli connection delete "NameOfWifi"
Offline
I experienced the same issue this year. Here is what I met. Hope useful.
1. When I connect to my school network (no encryption, public), everything normal.
2. I went home and tried to connect my home WiFi (WPA2-PSK), it failed. I used the following command:
$ nmcli device wifi connect <MySSIDAtHome> --askit asks me for passwd. Though I input the correct one, it immediately failed and asked me to input again, again and again.
3. I removed all previous MySSIDAtHome files at
/etc/NetworkManager/system-connections with root previleges and restarted NetworkManager.service using systemctl.
This time with the correct passwd,
$ nmcli device wifi connect <MySSIDAtHome> --asksucceeded. But Mouse Clicks on KDE GUI to forget-and-then-reconnect still fails.
Only with the command line with
--ask option can I reconnect my WiFi.
4. I tried to switch to iwd by changing configuration files at
/etc/NetworkManager/conf.d/wifi_backend.conf This time when I use
$ nmcli device wifi connect <MySSIDAtHome> without
--ask option, A KDE window prompted to ask me for passwd (despite warnings on terminal output).
I entered and it worked.
I then tried to forget-and-then-reconnect my WiFi in KDE GUI, and it also succeeded.
I think maybe it is a problem of the new --ask option, WPA2-PSK , and compatibility between NetworkManager and wpa_supplicant .
because
1. the older version did not meet this issue .
2. my school public network did not either.
3. iwd did not have the same issue as wpa_supplicant.
Hope these information useful.
Last edited by sgwzq (2026-01-26 16:19:28)
Offline
Please don't necro-bump
Moderator Note
closing this old thread
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online