GNOME Bugzilla – Bug 639336
Automatical connection to hidden network takes too long
Last modified: 2016-05-22 08:17:47 UTC
It seems as if the applet tries to connect to known hidden wireless networks after doing nothing for some time. Why cannot the applet start searching for the known hidden wireless networks just after starting?
Cleaning up the old bugs that didn't get addressed. Sorry you didn't hear from us. (In reply to Boris Kairat from comment #0) > It seems as if the applet tries to connect to known hidden wireless networks > after doing nothing for some time. > Why cannot the applet start searching for the known hidden wireless networks > just after starting? Because the network is hidden. It can not be searched for; we can only attempt an association. It's in fact what do we do now, so this is probably solved anyway. Please reopen if it's still a problem.
I want to reopen this bug, since it is not fixed: I'm on Arch Linux x86_64, gnome 3.20.2, networkmanager 1.2.2 I can't connect to my hidden wireless network. The only workaround I know makes NM connects to it, is using deprecated iwlist command: `sudo iwlist wlan0 scanning essid foo` where _wlan0_ is my network interface and _foo_ is the hidden network's name (I found this command elsewhere on the web...) I'm fully available to provide further information to solve this annoying issue!
(In reply to mattia.b89 from comment #2) > I want to reopen this bug, since it is not fixed: > > I'm on Arch Linux x86_64, gnome 3.20.2, networkmanager 1.2.2 > > I can't connect to my hidden wireless network. > The only workaround I know makes NM connects to it, is using deprecated > iwlist command: > `sudo iwlist wlan0 scanning essid foo` > where _wlan0_ is my network interface and _foo_ is the hidden network's name > (I found this command elsewhere on the web...) > > I'm fully available to provide further information to solve this annoying > issue! Hi mattia.b89, Also, the original bug is very old. Since then, much changed in NetworkManager handling hidden Wi-Fis. It is not clear that your issue is still the same as the original one (in fact, it's rather unlikely). Please open a new bug, describing better what you do, and attach a logfile of NetworkManager with TRACE logging enabled. Thank you.
I opened a new bug report as you suggested to do, here: https://bugzilla.gnome.org/show_bug.cgi?id=766564 let me know how can I help you