Bug 427512 - Unwanted automatic rearrange/sorting of items
Summary: Unwanted automatic rearrange/sorting of items
Status: RESOLVED DUPLICATE of bug 389052
Alias: None
Product: plasma-nm
Classification: Plasma
Component: applet (show other bugs)
Version: 5.19.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2020-10-10 13:04 UTC by Dan Snis
Modified: 2020-11-02 09:49 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
nm-applet (147.94 KB, image/png)
2020-10-10 13:04 UTC, Dan Snis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Snis 2020-10-10 13:04:05 UTC
Created attachment 132261 [details]
nm-applet

When clicking the network widget in the panel the first time (or after awhile) only my connected wifi network and configured VPNs show (see screenshot left).
After two to three seconds the list gets populated with the visible SSID, this rearrange the list.
So when I want to connect to my VPN (item number two in the list), I move my mouse pointer to the second row and when I'm about to press connect, the list updates and item number two is now another wifi network (screenshot right side).


STEPS TO REPRODUCE
1. open network list in panel
2. if you have a VPN configured and a second wifi network 'remebered' the list will reorder the items.


OBSERVED RESULT
Rearranged order of saved items

EXPECTED RESULT
Static arrangement of saved items/networks


SOFTWARE/OS VERSIONS
Windows: n/a
macOS: n/a
Linux/KDE Plasma: 5.8.12
(available in About System)
KDE Plasma Version: 5.19.90
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2020-10-12 18:38:25 UTC
Can confirm. This re-arrange sometimes mildly irritates me too and causes me to click on the wrong thing.
Comment 2 Justin Zobel 2020-11-01 04:19:19 UTC
This appears related to 389052
Comment 3 Dan Snis 2020-11-02 09:49:17 UTC
(In reply to Justin Zobel from comment #2)
> This appears related to 389052

I confirm. The same issue, sorry for the duplicate

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