From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: NetworkManager instead of Wicd in =?utf-8?Q?=E2=80=98%desktop?= =?utf-8?Q?-services=E2=80=99=3F?= Date: Fri, 04 Aug 2017 00:10:34 -0400 Message-ID: <87bmnw6khx.fsf@netris.org> References: <87iniaf06l.fsf@gnu.org> <87bmo1ltus.fsf@netris.org> <87k22p6mhf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43922) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ddTws-0003xI-1r for guix-devel@gnu.org; Fri, 04 Aug 2017 00:10:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ddTwo-0004vh-Rk for guix-devel@gnu.org; Fri, 04 Aug 2017 00:10:54 -0400 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Mark H Weaver skribis: > >> I've been using Network Manager with GNOME for several months at least, >> and generally I find it works very well, and reconnects much more >> quickly than wicd. > > Good. > >> However, there is one annoying bug: every time I reboot the system, the >> first 1-3 times it connects to the network, name lookups do not work. I >> always have to manually ask Network Manager to disconnect, and then >> reconnect. Sometimes I have to do this two or three times before name >> lookups work. After I've done this, it works perfectly until the next >> reboot. >> >> I looked into this a bit, but haven't yet found the cause. When name >> lookups are failing, /etc/resolv.conf exists and is correctly >> configured. I've tried restarting 'nscd', but it doesn't help. > > Weird. (I=E2=80=99ve installed GuixSD/GNOME/NM on a laptop that=E2=80=99= s almost always > on a wired network and it doesn=E2=80=99t have this problem AFAIK.) > > Could you enable nscd debugging output, so we can at least see whether > the problem is due to nscd caching name lookup failures? Something > like: > > (modify-services %desktop-services > (nscd-service-type config > =3D> (nscd-configuration > (inherit config) > (debug-level 3) > (log-file "/var/log/nscd.log")))) I've since migrated my x86_64 GuixSD system to building everything locally, using a local branch that's almost the same as 'core-updates' except with 'expat' and 'pcre' ungrafted. Since then, I've been unable to reproduce the problem I described above. However, I've run into a different problem. Several times, after reconnecting to the network, I've found that IceCat is unable to access the network (or possibly just DNS), even when the everything works from the command line. Restarting IceCat solves the problem. It's possible that waiting long enough would also work, but so far I haven't been patient enough to try it. Possibly related: the glibc-2.26 release announcement mentions the following new feature: * Improvements to the DNS stub resolver, contributed by Florian Weimer: - The GNU C Library will now detect when /etc/resolv.conf has been modified and reload the changed configuration. The new resolver option =E2=80=9Cno-reload=E2=80=9D (RES_NORELOAD) disables this behav= ior. Mark