GNOME Bugzilla – Bug 770938
When wifi activated NM connects to shared network without scanning for other networks
Last modified: 2017-06-16 09:57:52 UTC
When I turn the WiFi on, NM has a delay in scanning the available WiFi network, and at the beginning it only shows "local" networks (Shared networks, VPN). If one of this local networks is set to autoconnect, NM connects to it and doesn't perform the scan of the available WiFi networks. This causes two problems: - autoconnect priorities are ignored - to connect to another network, it's necessary to manually disconnect from the current network, perform a scan of the available Wifi networks and manually connect to one of them Scenario: SH1 shared Wifi network (autoconnect.priority 0) AP1 AP wifi network (autoconnect.priority 10) Steps: - Turn on Wifi Result: - NM connects to SH1 - NM doesn't perform the scan of the available WiFi networks, so that they are not listed - AP1 priority has been ignored Expected results: - NM perform the scan of available WiFi networks - NM connects to AP1 (highest priority available) - The list of WiFi network is shown so that it's possible to manually select another network
I've forget to say that I'm using KDE with plasma-nm as a NM client.
branch for review: https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=th/device-wifi-wait-for-scan-bgo770938
(In reply to Thomas Haller from comment #2) > branch for review: > https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=th/device- > wifi-wait-for-scan-bgo770938 LGTM
thanks. merged: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=fe6204ffc71f62c1667d0eba56f3a22d6aa9bbbd
Thanks! Can't wait to try this.
This bug is still present in networkmanager 1.8 using plasma-nm 5.10.1. If I'm not wrong that merge should be part of networkmanager 1.8, in this case the bug is not solved.
Yes, fe6204ffc71f62c1667d0eba56f3a22d6aa9bbbd is part of 1.8. If you experience a similar issue (be it the same cause, or just the same symptoms), you have to open a new bug and provide information on how to debug it. Especially that involves full logfiles with level=TRACE. See https://cgit.freedesktop.org/NetworkManager/NetworkManager/plain/contrib/fedora/rpm/NetworkManager.conf?id=master Thanks.
I missed that you are the original reporter :) In this case, please reopen the bug. But it still needs new information for debugging the issue (that is, the logfile and a fresh description of what you are doing precisely).
I've tried to reproduce it now, but I can't. Strangly I'm in the exact same condition where the bug appeared yesterday. So it seems to work. If it happens again I'll try to grab the log and I'll reopen the bug. Thank you.