Bug 453598 - Inputting a wifi password while the wifi list is refreshing can lead to the password being used for a different wifi connection than the one originally clicked
Summary: Inputting a wifi password while the wifi list is refreshing can lead to the p...
Status: RESOLVED DUPLICATE of bug 389052
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_networkmanagement (show other bugs)
Version: 5.24.4
Platform: Manjaro Linux
: NOR minor
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-09 20:03 UTC by papjk3@protonmail.com
Modified: 2022-05-10 15:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description papjk3@protonmail.com 2022-05-09 20:03:39 UTC
Inputting a wifi password while the wifi list is refreshing can lead to the password being used for a different wifi connection than the one originally clicked
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open the networks widget
2. Select a known router you wish to put in a password for to connect
3. Wait a bit for the wifi connections to be re-scanned (this needs change the wifi ap order)
4. Try to connect

OBSERVED RESULT
KDE will attempt to use the password for the known router to connect to a different unkown router that was in the same position in the list previously as the known router

EXPECTED RESULT
KDE will attempt to use the password for the known router instead of trying to connect to the unkown router because it was in the same list order

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: LTS 5.15.32-1 manjaro kernel
(available in About System)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
wifi 6 intel-based tp-link TX3000E
Comment 1 Nate Graham 2022-05-10 15:47:58 UTC

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