https://bugs.kde.org/show_bug.cgi?id=473184

            Bug ID: 473184
           Summary: Consistently position VPN connections in NM widget
    Classification: Plasma
           Product: plasma-nm
           Version: 5.27.1
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: applet
          Assignee: plasma-b...@kde.org
          Reporter: mikhail.kru...@seznam.cz
  Target Milestone: ---

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

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to