513116 2025-12-09 02:42:04 +0000 Network refreshing can re-order the list items just before you were about to click on one of them 2026-03-18 20:09:02 +0000 1 1 4 Plasma plasmashell Networks widget 6.5.3 Debian unstable Linux CONFIRMED https://bugs.kde.org/show_bug.cgi?id=390607 usability NOR normal 1.0 1 grundik plasma-bugs-null barto.gabriel kde nate 0 oldest_to_newest 2475395 0 grundik 2025-12-09 02:42:04 +0000 SUMMARY When networks list is refreshed, networks widget just renews. Often it happens right under the cursor, just before the click. So when I, for example, clicking to connect to one specific network, list suddenly refreshes the millisecond before I press the button, and click goes onto totally different network. There are no indications when list will be refreshed, it happens instantly and suddenly. STEPS TO REPRODUCE 1. open list of networks 2. point your cursor to some wifi network 3. wait a little OBSERVED RESULT Observe, when list refreshes, you are now pointing to different network (if unlucky), but you cant predict when it will happen. EXPECTED RESULT There should be some indication, that network scanning is in progress and list will be refreshed soon. Maybe by something like small progress bar, like in popup windows. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.9.2 ADDITIONAL INFORMATION This behavior was reported before, as part of https://bugs.kde.org/show_bug.cgi?id=390607 2475457 1 kde 2025-12-09 09:20:40 +0000 Unfortunately networkmanager doesnt expose the scanning state of the device. But since the applet requests scans itself it should be possible to do something 2475638 2 grundik 2025-12-09 21:18:35 +0000 Thank you for considering it. I can suggest possible solution: just show a progress bar for couple of seconds, as a warning. Yes, this will delay the refresh, but scanning is not instant anyways. Its possible to not wait, and refresh the list instantly, if cursor is away from the list. But this cant take into account possible touch input, so this approach are potentially problematic. 2504492 3 kdedev 2026-03-18 19:58:31 +0000 *** Bug 517429 has been marked as a duplicate of this bug. *** 2504498 4 barto.gabriel 2026-03-18 20:09:02 +0000 I noticed my bug (517429) was marked as a duplicate. I'd like to highlight that in my case, the issue isn't just the order of Wi-Fi networks, but that VPN connections are also getting mixed in with physical networks. This suggests the sorting/filtering logic is failing to distinguish between device types.