SUMMARY The "connect" context menu entry in the "WiFi & Networking" section when right-clicking a wifi network is sometimes mysteriously missing, see screenshot. My guess is perhaps it's already trying to connect to something, but 1. that shouldn't stop me from telling it to connect to something else, and 2. if i tell it to connect to something it's already connecting to it should just keep doing so. Therefore, it seems more confusing than helpful to me to make this entry disappear so often, especially since there seems to be zero indication or explanation anywhere under which conditions it is missing and why. STEPS TO REPRODUCE 1. Use "Wi-Fi & Networking" panel 2. Try to use "Connect" in context menu on wifi networks OBSERVED RESULT Half the time, the "connect" entry is missing. This even happens when there is no connecting spinner shown in the list. There doesn't seem to be any part of the UI telling the user why that is. Usually, a few seconds later it just reappears without explanation. EXPECTED RESULT "Connect" entry is always present, and clicking it when already connecting will either continue connecting (if same network) or abort and switch the target (if other network). SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: postmarketOS edge KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION
Created attachment 182027 [details] Screenshot with the context menu open and "Connect" missing. Network names have been blanked out via photo editing
Can confirm. I have "Connect" menu items for thew two wifi networks I regularly connect to, while all others lack it.
Reading the code, it looks like the menu item gets hidden for networks that aren't actually detected. Which makes sense; you can't connect to a network that isn't currently available! However this isn't great UX, since it's not clear why it's missing. Let's see if we can come up with something better. Maybe disable it and add a tooltip.
It seems like viewing the menu doesn't necessarily trigger a timely scan though, or if it does, it's not clear from the UI how long this would take. There's also no button to force a new scan if I know the network is available but wasn't picked up yet, which happens commonly. Perhaps it might make sense to show "Connect" always, and then just trying to re-scan and detect it, and showing some sort of feedback that it's not available if this process fails?
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-nm/-/merge_requests/434
Those are good ideas, and I can think of some others too: - Group networks in the list by availability - Add a "re-scan" button Unfortunately this KCM is pretty old and crusty so there's only so much we can really do with it. It just needs a modern rewrite.
Git commit e9fd4a4302f27f4f7c429ab345b29503683d1404 by Nate Graham. Committed on 09/06/2025 at 14:26. Pushed by ngraham into branch 'master'. kcm: explain why the "connect" context menu item can't be used Currently this menu item is hidden for networks that aren't detected, which makes sense. However the pattern may not be clear to the user. Instead, disable the menu item instead of hiding it, and add a tooltip explaining why it's disabled. FIXED-IN: 6.5.0 M +4 -1 kcms/kcm_connections/qml/ConnectionItem.qml https://invent.kde.org/plasma/plasma-nm/-/commit/e9fd4a4302f27f4f7c429ab345b29503683d1404