https://bugs.kde.org/show_bug.cgi?id=449265
--- Comment #14 from Alois Wohlschlager <alo...@gmx-topmail.de> --- (In reply to Shai from comment #13) > I have a similar issue -- in my case, a set of Samsung Galaxy phones (S20 > and S23) have been unable to connect for a few months; a laptop running > Debian testing could. That's quite interesting, this is the first report of the bug also depending on the client device. > I finally got tired of it and searched, and found this post on the Arch > Linux forums: > https://bbs.archlinux.org/viewtopic.php?id=293307 > > The original poster complains that his hotspot does not work when created > from KDE, but doing the same from Gnome does make it work. Thank you for this information, this is quite helpful since we can now determine what configuration can be applied to make it work. Notably, the configuration created by GNOME contains the following settings in its nmconnection file that the KDE one does not: group=ccmp; pairwise=ccmp; proto=rsn; > The reply says to run: > > nmcli connection modify WIFI-Share 802-11-wireless-security.proto wpa > > where "WIFI-Share" is the name of the WIFI configuration created for the > hotspot. I did that, and it solved the problem for me. This is not a very good idea, since it disables WPA2 and only leaves you with WPA. Can you try the following and report if and at what place things begin to work? (You either have to set up a fresh connection or undo the above command with 'nmcli connection modify WIFI-Share 802-11-wireless-security.proto ""' (two double quotes at the end).) nmcli connection modify WIFI-Share 802-11-wireless-security.group ccmp nmcli connection modify WIFI-Share 802-11-wireless-security.pairwise ccmp nmcli connection modify WIFI-Share 802-11-wireless-security.proto rsn > I should note that I encountered the problem at first a couple of years ago, > and then switching from wpa-supplicant to iwd mostly fixed things (it still > had minor issues). But for several months, this stopped working too. I wouldn't be surprised if the "several months" coincided with the release of iwd 2.18, which introduced WPA3 support. Can you confirm this if convenient? It would either mean that hostapd and iwd have the same bug, or it's at a lower level (driver, firmware or hardware). > Anyway, I find it hard to believe that the problem can be brushed aside as > "not in plasma" when it works in Gnome. The underlying bug unlikely to be in Plasma since the problem can be reproduced with plain hostapd without adding weird settings. That does not mean that Plasma can't add a workaround if an upstream fix can't be expected. Since you have figured out that it works in GNOME, that workaround could even consist of setting whatever GNOME does to make it work. -- You are receiving this mail because: You are watching all bug changes.
