Hi Vincent. I was just about to update this bug after purging wicd today.
On 20 April 2016 at 19:58, Vincent Lefevre <vinc...@vinc17.net> wrote: > > Probably the same bug as bug 557156 (from 2009!). The problem is that > wicd-daemon tries to reconfigure the ethernet interface even though > it is configured not to connect to it automatically (which should be > and is the default). A workaround is to remove eth0 from the wicd > configuration. > As far as I am aware, I have never touched the wicd config files. And a package shouldn't ship with a config that will break an otherwise valid configuration belonging to a different package on package upgrade. Certainly not without _big_ warnings, and certainly not for a package pulled in by recommendations from a relatively common metapackage. (I included a copy of the relevant config files at the bottom of the original bug report). Now for the new stuff. Today I removed wicd and related packages. I'm pretty sure I purged the config files. To cut a long story short, purging wicd and related packages resulted in eth0 having it's IPv4 address removed. Eth0 was still up with a IPv6 address. But the machine was no longer reachable over IPv4. Probably just a different variant of the same underlying buggy behaviour. Thanks for your work on Debian. Andrew V.