https://bugs.kde.org/show_bug.cgi?id=449265
--- Comment #15 from Shai <s...@platonix.com> --- Hi, Thanks, this is very helpful! (In reply to Alois Wohlschlager from comment #14) > (In reply to Shai from comment #13) > > 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. Thanks for the heads-up! > 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 > Will check later, when it's more convenient. > > 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). > I can't be completely sure -- but I upgraded from iwd 2.17 to 2.19 on July 21, and removed iwd (that is, gave up on trying to make it work) on August 16 (the system providing the hotspot is also Debian testing). > > 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. FWIW I don't have hostapd installed, and never heard of it before the searches I did yesterday. > 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. That makes perfect sense (except credit for finding that it works in Gnome should go to Vamp898 from the Arch Linux forum). Thanks! -- You are receiving this mail because: You are watching all bug changes.
