I have recently been having issues with with wifi on fedora 44 KDE. For the most part the wifi works perfectly fine but the issues seem to come up whenever I am traveling with the laptop. The main most noticeable issue is that when I dive home the laptop can no longer connect home wifi network and seems to have password issues which is strange since the wifi password is correct. Restarting network manager does not fix this and the laptop can connect to other networks but the issue only goes away after a full restart of the laptop. I tried to replicate the issue by taking the laptop driving away and driving back but it never seems to work. The only times this issue comes up is if I connect to work wifi then drive back or connect to university wifi and drive back connecting to other wifi networks do not seem to cause the issue. I also tried messing with all of the security settings and mimicking the settings of other devices that do work on the network including my phone and changing Bands but none of that seemed to do the trick and the only real solution I found is doing a full reboot.
The security settings on the networks that I think lead to this breaking are using WPA2-EAP with a username and password. The home network that seems to be getting problems from this is using WPA-2.
Can you share the output of
journalctl -u NetworkManager -b | grep -i "secret\|auth\|eap\|fail"
Sure, the network that is having the issues is the ATTvuvd5JI one.
Aug 27 12:17:02 hatlaptop NetworkManager[1288]: [1787858222.1479] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.3/PNP0C09:00/VPC2004:00/rfkill/rfkill0) (platform driver ideapad_acpi)
Aug 27 12:17:06 hatlaptop NetworkManager[1288]: [1787858226.0472] device (wlo1): Activation: (wifi) access point ‘ATTvuvd5JI’ has security, but secrets are required.
Aug 27 12:17:06 hatlaptop NetworkManager[1288]: [1787858226.0472] device (wlo1): state change: config → need-auth (reason ‘none’, managed-type: ‘full’)
Aug 27 12:17:06 hatlaptop NetworkManager[1288]: [1787858226.0485] device (wlo1): state change: need-auth → prepare (reason ‘none’, managed-type: ‘full’)
Aug 27 12:17:06 hatlaptop NetworkManager[1288]: [1787858226.0552] device (wlo1): Activation: (wifi) connection ‘ATTvuvd5JI’ has security, and secrets exist. No new secrets needed.
Aug 27 12:17:06 hatlaptop NetworkManager[1288]: [1787858226.2457] device (wlo1): supplicant interface state: scanning → authenticating
Aug 27 12:17:06 hatlaptop NetworkManager[1288]: [1787858226.2458] device (p2p-dev-wlo1): supplicant management interface state: scanning → authenticating
Aug 27 12:17:06 hatlaptop NetworkManager[1288]: [1787858226.2507] device (wlo1): supplicant interface state: authenticating → associating
Aug 27 12:17:06 hatlaptop NetworkManager[1288]: [1787858226.2507] device (p2p-dev-wlo1): supplicant management interface state: authenticating → associating
Aug 27 12:37:36 hatlaptop NetworkManager[1288]: [1787859456.8132] device (p2p-dev-wlo1): state change: disconnected → unavailable (reason ‘supplicant-failed’, managed-type: ‘full’)
Aug 27 12:37:48 hatlaptop NetworkManager[1288]: [1787859468.2173] device (wlo1): Activation: (wifi) access point ‘ATTvuvd5JI’ has security, but secrets are required.
Aug 27 12:37:48 hatlaptop NetworkManager[1288]: [1787859468.2173] device (wlo1): state change: config → need-auth (reason ‘none’, managed-type: ‘full’)
Aug 27 12:37:48 hatlaptop NetworkManager[1288]: [1787859468.2190] device (wlo1): state change: need-auth → prepare (reason ‘none’, managed-type: ‘full’)
Aug 27 12:37:48 hatlaptop NetworkManager[1288]: [1787859468.2255] device (wlo1): Activation: (wifi) connection ‘ATTvuvd5JI’ has security, and secrets exist. No new secrets needed.
Aug 27 12:37:48 hatlaptop NetworkManager[1288]: [1787859468.3204] device (wlo1): supplicant interface state: scanning → authenticating
Aug 27 12:37:48 hatlaptop NetworkManager[1288]: [1787859468.3205] device (p2p-dev-wlo1): supplicant management interface state: scanning → authenticating
Aug 27 12:37:48 hatlaptop NetworkManager[1288]: [1787859468.3272] device (wlo1): supplicant interface state: authenticating → associating
Aug 27 12:37:48 hatlaptop NetworkManager[1288]: [1787859468.3272] device (p2p-dev-wlo1): supplicant management interface state: authenticating → associating
Aug 27 14:09:10 hatlaptop NetworkManager[1288]: [1787864950.4153] device (wlo1): Activation: (wifi) access point ‘ATTvuvd5JI’ has security, but secrets are required.
Aug 27 14:09:10 hatlaptop NetworkManager[1288]: [1787864950.4153] device (wlo1): state change: config → need-auth (reason ‘none’, managed-type: ‘full’)
Aug 27 14:09:10 hatlaptop NetworkManager[1288]: [1787864950.4166] device (wlo1): state change: need-auth → prepare (reason ‘none’, managed-type: ‘full’)
Aug 27 14:09:10 hatlaptop NetworkManager[1288]: [1787864950.4169] device (wlo1): Activation: (wifi) connection ‘ATTvuvd5JI’ has security, and secrets exist. No new secrets needed.
Aug 27 14:09:10 hatlaptop NetworkManager[1288]: [1787864950.5200] device (wlo1): supplicant interface state: scanning → authenticating
Aug 27 14:09:10 hatlaptop NetworkManager[1288]: [1787864950.5200] device (p2p-dev-wlo1): supplicant management interface state: scanning → authenticating
Aug 27 14:09:10 hatlaptop NetworkManager[1288]: [1787864950.5258] device (wlo1): supplicant interface state: authenticating → associating
Aug 27 14:09:10 hatlaptop NetworkManager[1288]: [1787864950.5258] device (p2p-dev-wlo1): supplicant management interface state: authenticating → associating
Thanks, iam not an expert on this one but, the wpa_supplicant is failing not the Network Manager, NM thinks that those secrets are fine and hands them to wpa_supplicant but it can’t complete the association.
If you look it, the pattern is always
secrets are required → secrets exist. No new secrets needed → authenticating → associating
there is no connected or failed status.
It might be that wpa_supplicant is stuck witht he stale state from EAP network and cant switch cleanly to your home wifi.
The next time please check if restarting the wpa_supplicant fixes this or not.
sudo systemctl restart wpa_supplicant
EDIT : REPLIED TO MYSELF INSTEAD OF OP (oops)
Ok I will try and see if this works next time I can re-create the issues but for some reason it basically only happens with those two networks in that order when I drive other places with the laptop the issue just does not appear really.
Hello, any updates?
Not really since the past few days I have not been able to reliably replicate the issue. I believe that either an update or either some slight tweaks to the system resolved most of the issue but that does surprise me because I have not really updated many packages that I would have thought would fix the issue like a kernel update but as of right now the problem is gone.