Bug#838552: wicd runs disconnect scripts between pre- and postconnect

[Axel Beckert <abe@debian.org>]

Hi Martin,

martin f krafft wrote:
> I have a simple debug script in all four of the wicd script
> directories, which does nothing other than
> 
>   echo "*** $IFACE *** $0 $@ ($date -R)" >> /tmp/wicd.debug
> 
> If I plug in a cable, the following happens:
> 
>   2016-09-22T10:37:14,069870858+02:00 *** cable *** /etc/wicd/scripts/predisconnect/local-debug.sh wired wired wired
>   2016-09-22T10:37:14,578834082+02:00 *** cable *** /etc/wicd/scripts/postdisconnect/local-debug.sh wired wired wired
>   2016-09-22T10:37:14,630906594+02:00 *** cable *** /etc/wicd/scripts/preconnect/local-debug.sh wired wired wired-default
>   2016-09-22T10:37:16,779792523+02:00 *** cable *** /etc/wicd/scripts/predisconnect/local-debug.sh wired wired wired
>   2016-09-22T10:37:17,275810373+02:00 *** cable *** /etc/wicd/scripts/postdisconnect/local-debug.sh wired wired wired
>   2016-09-22T10:37:23,435090285+02:00 *** cable *** /etc/wicd/scripts/postconnect/local-debug.sh wired wired wired-default
> 
> Please note how first pre-/postdisconnect are run. Why is that? The
> cable had long before been disconnected, so while this is not a big
> deal, it seems wrong.

Well, I'd call it debatable. I also see reasons for this behaviour.

> What's worse though is that the pre-/postdisconnect scripts are run
> *again* after preconnect and before postconnect, which can break
> some applications, e.g. enabled ipv6 autoconf in preconnect and
> turning it off in postdisconnect.

Thanks for this very precise bug report. The latter behaviour indeed
sounds wrong and may explain some other reported or seen issues. Will
have a look at it.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE