Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.
Hi Andrew,
Andrew Vaughan wrote:
> My home server is a headless box, administered from a vnc session tunnelled
> over ssh. It has no wifi adaptor, just a single ethernet port that is
> statically configured via /etc/network/interfaces.
So why are you using wicd at all? I don't see why you need wicd in
such a setup.
> This behaviour is wrong on so many levels.
>
> 1. A package upgrade should never bring down an existing in-use interface
> without asking the user/admin first.
I agree here mostly. It's though only a real issue if the interface
doesn't come up again with the same IP afterwards.
> 2. I don't think I have ever actually used wicd.
See my question above. You don't need it.
> Wicd-daemon should not assume that just because it is installed it
> owns all the network interfaces.
I disagree here. In Debian, it's common that NetworkManager and
similar tools manage those interfaces from /etc/network/interfaces
which are not listed (or maybe also those which are on "auto").
The issue here seems that wicd seems to no more blacklists them. Will
have to check.
> I have been through basically the same problems with network-manager in the
> past. Issues like this are why so many people are hostile to that package.
Indeed. That's why I'm using wicd, too. It was though worse with
NetworkManager back then since usually, the network interface stayed
down afterwards. That got fixed in the meanwhile, though, IIRC.
For now I've forwarded this issue to upstream at
https://bugs.launchpad.net/wicd/+bug/1553761
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
Reply to: