On 2015-09-06 22:53:18 +0200, Guus Sliepen wrote: > On Sun, Sep 06, 2015, Alain Rpnpif wrote: > > Some people suggest me to remove ifupdown instead of wicd. I prefer to > > keep ifupdown and remove wicd and it works fine. But I do not know the > > cause because I have seen nothing in logs. > > > > I could try wicd alone. > > In general, you can use both simultaneously, but not on the same > interface. But until this bug is fixed, I think you should try using > either wicd alone or ifupdown alone. If you want to use wicd, then you > don't have to remove the ifupdown package, but just remove the eth0 and > wlan0 stanzas.
I confirm that running both simultaneously is OK if they don't manage the same interface. In my case, I use ifupdown for eth0, and wicd for WiFi connections. In the wicd preferences, the "Wired interface" field is blank to make sure that wicd won't do anything concerning eth0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557156#22 I've doing that for more than 3 years (on two different laptops) and everything has always been fine with this setting. -- 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)
