Bug 471378 - Entering the wrong wifi password takes a long time to show you an error and ask again
Summary: Entering the wrong wifi password takes a long time to show you an error and a...
Status: RESOLVED FIXED
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2023-06-23 11:41 UTC by aronkvh
Modified: 2023-12-11 16:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aronkvh 2023-06-23 11:41:25 UTC
If you enter the wrong the password for a wifi network, it just says configuring interface and doesn`t tell you that the password is incorrect and couldn`t connect.
Comment 1 David Redondo 2023-12-05 12:14:28 UTC
I am afraid I can't reproduce it, if I enter a wrong password, a dialog opens prompting me for a password. The same happens if I enter a wrong password that dialog.
Comment 2 David Redondo 2023-12-05 12:14:57 UTC
Maybe you can give more details (including networkmanager version)?
Comment 3 Nate Graham 2023-12-08 05:43:30 UTC
I also get the dialog eventually, but it takes like 30 seconds. NetworkManager 1.44.2.
Comment 4 Bug Janitor Service 2023-12-11 15:26:16 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-nm/-/merge_requests/312
Comment 5 David Redondo 2023-12-11 16:01:49 UTC
Git commit 2ca168be630d394066697d4ab26909a9d54c1a06 by David Redondo.
Committed on 11/12/2023 at 16:15.
Pushed by davidre into branch 'master'.

If the user provided password was incorrect say so in the dialog

RequestNew is documented as "This flag signals that NetworkManager
thinks any existing secrets are invalid or wrong". We can use this
information to show a better string.

M  +11   -2    kded/passworddialog.cpp

https://invent.kde.org/plasma/plasma-nm/-/commit/2ca168be630d394066697d4ab26909a9d54c1a06
Comment 6 Nate Graham 2023-12-11 16:05:19 UTC
From my perspective, this is fully fixed by the above commit. Thanks David!