On 2019-07-14 15:30:01 +0200, Axel Beckert wrote: > > 2019/07/14 12:42:53 :: Gemini WiFi has profile > > I assume "Gemini WiFi" is the essid of your described setup.
Yes. > > 2019/07/14 12:42:53 :: Unable to autoconnect, you'll have to manually > > connect > [...] > > 2019/07/14 12:42:58 :: Gemini WiFi has profile > > 2019/07/14 12:42:58 :: Unable to autoconnect, you'll have to manually > > connect > [...] > > 2019/07/14 12:43:03 :: Gemini WiFi has profile > > 2019/07/14 12:43:03 :: Unable to autoconnect, you'll have to manually > > connect > > So I suspect that finding the reason for the "Unable to autoconnect, > you'll have to manually connect" message is what would help to solve > this. Obviously the log should give the reason. > > Note: I think that wicd will automatically reconnect when the option > > "Automatically connect to this network" for the network is on, just > > because of that, independently from the "Automatically reconnect on > > network connection loss" global setting. Thus make sure that this > > option "Automatically connect to this network" for the tested network > > is off when doing the test. > > Hrm, you've got a point there, but I'm not sure if this is by design. This is *not* by design, as clearly documented in the wicd(8) man page: "even if that network does not have automatic connection enabled". The man page then says: "should that fail, it will try both a wired connection and any available wireless networks which have automatic connection enabled.", which could explain why it works when "Automatically connect to this network" in on for the considered network. > Being picky you could say that "Automatically reconnect on network > connection loss" should only work for wifi networks where > "Automatically connect to this network" is set, too. But for some reason, this is not what I want (e.g. I don't want to auto-connect to some networks after start up). > There is also this rather old bug report at > https://bugs.launchpad.net/wicd/+bug/480097 and > https://bugs.debian.org/544410 which might be related. The one on > launchpad is still open, the one in the Debian BTS has been closed, > because two of the reporters could no more reproduce it without any > code change. This one could also be the bug when the GUI is open. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
