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: Sun, 30 Jul 2017 13:25:47 -0400 Message-ID: <87bmo1ltus.fsf@netris.org> References: <87iniaf06l.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]:60873) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dbryp-0006Rv-Bv for guix-devel@gnu.org; Sun, 30 Jul 2017 13:26:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dbryl-0007NF-83 for guix-devel@gnu.org; Sun, 30 Jul 2017 13:26:15 -0400 In-Reply-To: <87iniaf06l.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 30 Jul 2017 16:50:58 +0200") 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: > Shouldn=E2=80=99t we replace Wicd with NetworkManager in =E2=80=98%deskto= p-services=E2=80=99? > > I=E2=80=99ve given it a try on a GuixSD GNOME installation and it appears= to > work well, and it=E2=80=99s obviously well-integrated with GNOME, whereas= Wicd > is a bit hidden (one has to know what to look for) and =E2=80=9Cforeign.= =E2=80=9D > > Thoughts? 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. 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. One caveat: for some time now I've only tested Network Manager with wired networks. I've recently been unable to use wireless, because I had to replace the motherboard in my Thinkpad X200, and haven't yet gotten around to getting the clip I need to reflash Libreboot. The proprietary BIOS refuses to boot with the Atheros wireless card installed, so I had to remove the card for now. > Now, as someone who doesn=E2=80=99t use GNOME, I wonder if NM would work = well > for me. Last time I tried it=E2=80=99s CLI was too low-level to be usabl= e, and > I don=E2=80=99t remember seeing a curses interface. Suggestions? There is a curses interface included with Network Manager. It's called 'nmtui'. It's not getting built because it depends on 'newt', which is not an input to our Network Manager package. Mark