[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#704211: [release-notes] [wheezy] issues: NM conflicts with wicd-daemon, Gnome3 now depends on NM

On Du, 07 apr 13, 12:10:28, Chris Knadle wrote:
> On Sunday, April 07, 2013 02:22:17, Andrei POPESCU wrote:
> > On Vi, 29 mar 13, 09:45:11, Chris Knadle wrote:
> > > You will also need to recreate /etc/resolv.conf, as the contents of this
> > > file is replaced by NetworkManager.
> > 
> > Isn't this done by wicd-daemon (maybe by restarting it)?
> It doesn't.  Also keep in mind that wicd can be set for all kinds of 
> configurations, such that it may not touch this file even making a connection.  
> [I have what appear to be default settings, and this is the behavior I see on 
> my home network, for instance.]

This doesn't sound right. Wicd has got to have some resolv.conf 
handling, otherwise it wouldn't be very useful. Maybe the maintainer can 
help out here?
> /By default/ NM seems to replace /etc/resolv.conf on the first connection 
> attempt.
> This entry in the release-notes is aimed for Gnome users that /didn't/ 
> previously have network-manager installed, thus may be using wicd.  The first 
> thing these users are likely to do is try wicd and find it broken due to the 
> conflict, then try NM and find it broken too -- and the connection attempt 
> with NM replaces the /etc/resolv.conf file, where wicd may not.

Kept for a little bit more context.

Kind regards,
Offtopic discussions among Debian users and developers:

Attachment: signature.asc
Description: Digital signature

Reply to: