Bug 505226

Summary:	Network Dialog Displays Incorrect Security Type when using iwctl
Product:	[Plasma] plasmashell	Reporter:	Zach <sdudexd>
Component:	Networking in general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	gbeintmann, kdedev, uhhadd
Priority:	NOR
Version First Reported In:	6.2.5
Target Milestone:	1.0
Platform:	SteamOS
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	6.5.0
Sentry Crash Report:

Description Zach 2025-06-05 04:23:03 UTC

SUMMARY
I noticed that when connecting to my WIFI which is set to WPA2/WPA3-Personal, on my Steamdeck using KDE plasma (Steamos), that when I specify WPA3 to use, it displays as "Security type: Insecure". I was concerned about this so I posted about it on Reddit, and then found that it was using WPA2 via the command line, but displaying "Insecure" in the GUI.

STEPS TO REPRODUCE
1. Set up WIFI via GUI (Wifi and networking)
2. Manually specify to connect using security type WPA3-Personal
3. See it is incorrectly displayed in the GUI.

OBSERVED RESULT
The GUI shows the listed security type as "Insecure" and not "WPA3-Personal/WPA2-Personal"

Listed in terminal (using nmcli dev wifi list):
It shows the AP using WPA2 security type.

EXPECTED RESULT
The GUI should display the security type as "WPA2-Personal"

SOFTWARE/OS VERSIONS
SteamOS: 3.7.9 Build: 20250527.1
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1

ADDITIONAL INFORMATION
My router is set to WPA2&WPA3 so that older HW can use WPA2 as a fallback.
Displayed on my phone is that it is using WPA3 (SAE transition mode) and I suspect as well as the help I got on reddit, that due to it using this mode, KDE is incorrectly falling back saying it is "Insecure" and not "SAE transition mode" possibly?.

I have added the IMGUR link that I used on reddit which shows screenshots of the problem with annotations.
https://imgur.com/a/KOdOgfa

Comment 1 Bug Janitor Service 2025-06-05 04:33:37 UTC

Thank you for the bug report!

However Plasma 6.2.5 is no longer eligible for support or maintenance from KDE; supported versions are 5.27. (LTS), and 6.3 (non-LTS) or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need support for Plasma 6.2.5, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE.

If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report.

Comment 2 Gordon 2025-07-19 05:56:12 UTC

This issue is still present as of 6.4.3 on Arch Linux. 
Can also confirm that the issue is not limited to APs using WPA2/3 mixed mode, as it also occurs with WPA2 only.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.6-arch1-1 (64-bit)
Graphics Platform: Wayland

Using NetworkManager with iwd.

Comment 3 TraceyC 2025-08-08 20:24:09 UTC

I confirm this bug on 6.4.3
I'm currently connected to a Wi-Fi access point which uses WPA2. The details of the connection in the widget show "Security Type: Insecure"

The good news it that I cannot reproduce this on git-master. For the same Wi-Fi access point, I see
"Security Type: WPA2-PSK"

This will be fixed when Plasma 6.5.0 is published. This should be fixed on your system when your distro has updated to that version of Plasma. If the bug is still present on your system with that or a later version, please feel free to reopen this bug report.

Comment 4 Gordon 2025-10-30 10:09:34 UTC

This issue is still present as of 6.5.1 on Arch Linux. 

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.5-arch1-1 (64-bit)
Graphics Platform: Wayland

Using NetworkManager with iwd.

Comment 5 TraceyC 2025-11-07 18:05:48 UTC

Thanks for the update. I'm still not able to reproduce this in git-master, but I don't have a real WPA2 network to test with. Hopefully someone who does have access to this kind of network can try.

Comment 6 TraceyC 2025-11-07 22:14:31 UTC

I was pointed at another report, bug 491678, which seems to be the same bug. I'll merge this report in with that one.

*** This bug has been marked as a duplicate of bug 491678 ***