Debian Bug report logs - #932042
wicd-daemon: does not automatically reconnect on network connection loss if this network is invisible during the unique attempt

Full log

Message #27 received at [email protected] (full text, mbox, reply):

Received: (at 932042) by bugs.debian.org; 14 Jul 2019 18:39:56 +0000
From [email protected] Sun Jul 14 18:39:56 2019
X-Spam-Checker-Version: SpamAssassin 3.4.2-bugs.debian.org_2005_01_02
	(2018-09-13) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-12.4 required=4.0 tests=BAYES_00,FOURLA,
	HAS_BUG_NUMBER,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham
	autolearn_force=no version=3.4.2-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 8; hammy, 150; neutral, 127; spammy,
	0. spammytokens: hammytokens:0.000-+--H*F:D*vinc17.net,
	0.000-+--H*rp:D*vinc17.net, 0.000-+--HX-Mailer-Info:mutt,
	0.000-+--HX-Mailer-Info:www.vinc17.net, 0.000-+--H*M:vinc17
Return-path: <[email protected]>
Received: from joooj.vinc17.net ([2001:4b99:1:3:216:3eff:fe20:ac98])
	by buxtehude.debian.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.89)
	(envelope-from <[email protected]>)
	id 1hmjPf-0001TR-SK
	for [email protected]; Sun, 14 Jul 2019 18:39:56 +0000
Received: from smtp-zira.vinc17.net (unknown [37.164.59.198])
	by joooj.vinc17.net (Postfix) with ESMTPSA id 8177B2A6;
	Sun, 14 Jul 2019 20:39:53 +0200 (CEST)
Received: by zira.vinc17.org (Postfix, from userid 1000)
	id 28745C2017E; Sun, 14 Jul 2019 20:39:52 +0200 (CEST)
Date: Sun, 14 Jul 2019 20:39:52 +0200
From: Vincent Lefevre <[email protected]>
To: Axel Beckert <[email protected]>
Cc: [email protected]
Subject: Re: [pkg-wicd-maint] Bug#932042: wicd-daemon: does not automatically
 reconnect on network connection loss when this is enabled
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <[email protected]>
X-Mailer-Info: https://www.vinc17.net/mutt/
User-Agent: Mutt/1.12.1+33 (6a74e24e) vl-117499 (2019-06-23)

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 <[email protected]> - 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)

Send a report that this bug log contains spam.