Bug 473184

Summary: Consistently position VPN connections in NM widget
Product: [Plasma] plasmashell Reporter: Mike Krutov <nekoxmachina>
Component: Networks widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Mike Krutov 2023-08-09 00:54:24 UTC
SUMMARY
VPN Connections are not positioned consistently. If a user clicks on "Connect to VPN" button during a wireless refresh, when new networks are populating the widget, it is entirely possible to click "connect" on a different Wireless network instead of connecting/disconnecting to VPN


STEPS TO REPRODUCE
1. Have a few wifi networks around
2. Have a VPN connection configured
3. Connect to WiFi#1. This results in following order:
a. WiFi#1
b. Your VPN network.
c. All the other WiFis.

4. Wait abit for system to refresh the list of WiFi networks. 


OBSERVED RESULT
When refresh is in progress, there are 2 items displayed in this order: 
1) WiFi#1
2) Your VPN connection

When refresh is finished, following order is observed:

1) WiFi#1
2) ALL the other WiFi's
3) VPN connection

As the refresh happens pretty fast, I constantly click on the first wifi in list instead of connecting to my VPN network when this sequence of events happens. 

EXPECTED RESULT
Order of networks as follows:
1) Networks device is currently connected to
2) Virtual networks
3) Networks with saved configuration (i.e. WiFi#2 which user already has connected to in the past)
3) All the other networks.

As items 1) and 2) are constant for a "refresh" state of widget, this would ensure that the positioning of all the elements is as static as possible. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 

KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-08-09 19:15:16 UTC

*** This bug has been marked as a duplicate of bug 435475 ***
Comment 2 Ben Cooksley 2024-12-23 18:25:54 UTC
Bulk transfer as requested in T17796