Bug 424951 - Wifi scanning makes me click the wrong VPN connection
Summary: Wifi scanning makes me click the wrong VPN connection
Status: RESOLVED DUPLICATE of bug 389052
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: 5.16.5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2020-08-03 04:36 UTC by Phil
Modified: 2020-11-19 22:14 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 Phil 2020-08-03 04:36:02 UTC
SUMMARY

When I want to connect to an existing VPN, I click the applet icon and then click the VPN connection I want (often the first one under "Available connections"). However, due to wifi scanning, a wifi connection suddenly appears in its place and I click on that instead which is almost as infuriating as when I accidentally click an ad because my browser re-arranged a page while loading.

STEPS TO REPRODUCE
1. Have a wifi connection available (but not currently connected. This often happens if you have a 2.4/5g router).
2. Click applet with the intent to connect to a VPN
2. Click on the VPN to initiate the connection
3. Realise wifi scanning changed the order and you have accidentally clicked on the wrong item
4. Be frustrated enough to file a bug report

OBSERVED RESULT

Clicked on the wrong network connection

EXPECTED RESULT

Items do not suddenly change so that the user can click on the wrong item. I wont pretend to be a UI expert and come up with an alternative for the UI, but re-arranging items after presenting them to the user is a good way for them to click on the wrong one.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Kubuntu 19.10
(available in About System)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4
Comment 1 postix 2020-08-03 12:21:16 UTC
I can confirm this issue as it happend at least twice to me too.
Comment 2 Justin Zobel 2020-11-19 22:14:00 UTC

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