SUMMARY When a network has been added to the list of known networks with a key, a rogue access point with the same SSID, but a different key will seduce plasma-nm to invoke a popup and ask the user for a new key. This *might* make sense, in certain circumstances - for example when the user just changed the wifi-hotspot key. But in most cases, this is either just a temporary error while a hotspot restart or a name collision for the SSID. STEPS TO REPRODUCE 1. Create a network with a WPA(2)-PSK key 2. Connect to it 3. Add a second network with the same SSID but a different WPA(2)-PSK key 4. Turn off the first one OBSERVED RESULT A popup will appear and ask for the network key EXPECTED RESULT Plasma-nm should instead silently ignore the error, add the hotspot to a blacklist for a short duration of time (like 60 seconds) and try other hotspots of this SSID. If the user opens the panel with the networks a simbol might be added for such situations with an icon like a triangle with a hint like: "Connection issues, maybe wrong network key?" With a click a user might then get a popup: With "If you changed the network key, enter the new one here: " And a button for help, which explains why this error popped up and what this might mean. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.4.1 KDE Frameworks Version: 5.18.4.1 Qt Version: 5.14.2
Bulk transfer as requested in T17796