Bug 506647

Summary:	Cant connect to 5Ghz wifi network
Product:	[Plasma] plasmashell	Reporter:	geopapougr
Component:	Networking in general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	kdedev, nate, realkpavel
Priority:	NOR
Version First Reported In:	6.4.1
Target Milestone:	1.0
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description geopapougr 2025-07-05 18:05:45 UTC

SUMMARY
I have a T490. It can detect 5Ghz networks. I also have a wifi/bluetooth TP dongle capable of 5Ghz as well. Both of them fail to connect to my homes 5Ghz network. I think that in the previous days, I was able to connect to 5ghz networks so this might be an issue that doesnt always happen. I tried using my phone as a hotspot on 5Ghz and the same issue exists. 2.4Ghz works completely fine.

As for the issue itself, what happens is that whether the network is known or not, when I try to connect, it just tries to connect infinitely. What I tried is logging in with nmcli. It said that 802-11-wireless-security.key-mgmt property is missing. When I try to connect without specifying the password in the connect command itself, and instead I use "--ask", it prompts me for a password and it connects every time.

One thing I noticed, is that for my laptops wifi card, even when I have connected with "--ask" before, I cant disconnect and reconnect, whereas my wifi dongle can do so.

This could be a nmcli issue since that fails as well. But I need help on where to guide this bug and info.

STEPS TO REPRODUCE
1. Diconnect from your wifi network
2. Find a 5Ghz wifi network that you own and know the password
3. Click to connect using the KDE UI
4. Enter the password when prompted

OBSERVED RESULT
Limited connectivity message appears and "Configuring interface" with an infinitely lasting loading circle.

It also randomly disconnects and try to connect again after some seconds

EXPECTED RESULT
Proper wifi connection

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 42
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Thinkpad T490 with Wifi 5 card, integrated.
Kernel: 6.14.9-300.fc42.x86_64

Comment 1 Kat Pavlu 2025-07-06 09:02:49 UTC

Since this also fails with nmcli, this is almost certainly an issue in the NetworkManager backend. 

A simple way to test if this is a networkmanager thing would be booting up a Fedora Workstation image (Gnome also uses networkmanager) with the same package versions. If the issue is present there too, then this has to be in the shared backend. Live ISOs with updated packages can be found here https://dl.fedoraproject.org/pub/alt/live-respins/

If the issue is present on both, please report back, and then I sugest you report this directly to Fedora (https://docs.fedoraproject.org/en-US/quick-docs/bugzilla-file-a-bug/).

Comment 2 geopapougr 2025-07-11 07:26:29 UTC

I did some tests.

On my laptop, I use Aurora. I now updated it, clicked forget network (for the 5Ghz) and I was able to connect with the UI. So the issue doesn't seem to exist on the updated version.

From the images you provided, I tried budgie, KDE again and also went and downloaded Fedora workstation, which has Ubuntu.

Budgie worked for both 2.4Ghz and 5Ghz with the UI. Ubuntu as well. One thing I did on either case is connect to 2.4Ghz and update my packages, to simulate what happened to me on Aurora before.

KDE failed to connect to both 2.4Ghz and 5Ghz. I tried to connect with nmcli, both with setting the password in the command itself and with --ask, and I didnt manage to connect. But I got a different error this time.

I find it weird that KDE is the only DE that failed. Shall I provide more info or is this an issue to be discarded? Are the .iso files supposed to work or is it fine if they dont?

Comment 3 Bug Janitor Service 2025-07-26 03:46:33 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Nate Graham 2025-08-07 18:10:11 UTC

Indeed this seems like a combination of a NetworkManager and local configuration issue. I'd recommend taking it to your distro or https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues.