From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Network Manager Service Date: Thu, 24 Nov 2016 22:02:58 +0100 Message-ID: <87lgw8wpz1.fsf@gnu.org> References: <3bc5b721a8b3a69692e3bf52b13bc5f0@openmailbox.org> <87lgwd1at2.fsf@gnu.org> <874m31xijr.fsf@gmail.com> <87y40dvt1d.fsf@gnu.org> <4fafee90348a41b9cebf93bdefc8fd76@openmailbox.org> <87mvgq7ebm.fsf@gnu.org> <87k2bth1ai.fsf@gmail.com> 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]:38846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cA1Af-00065v-0W for help-guix@gnu.org; Thu, 24 Nov 2016 16:03:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cA1Ab-0008Uf-2U for help-guix@gnu.org; Thu, 24 Nov 2016 16:03:05 -0500 In-Reply-To: <87k2bth1ai.fsf@gmail.com> (Chris Marusich's message of "Wed, 23 Nov 2016 21:52:53 -0800") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Chris Marusich Cc: rennes@openmailbox.org, help-guix@gnu.org Chris Marusich skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> Oops, I had left an extra #:use-module line in there, sorry! >> >> Could you try this one? > > On my GuixSD system, The new patch works with one problem: Network > Manager still does not show any wireless networks. I solved this by > adding wpa-supplicant-service (this service was mentioned in the manual, > but it was actually missing from code!) and making > 'network-manager-shepherd-service' require it. Here's the updated > patch: Good catch! I pushed these changes like this: cbf1024 * doc: Document 'wpa-supplicant-service-type'. 030f59f * services: network-manager: Depend on 'wpa-supplicant'. 89007a0 * services: network-manager: Install polkit actions. 2e32869 * services: Move polkit to (gnu services dbus). > However, there is one problem: Even if I select "Connect automatically" > (in the "Identity" section of the settings page within Network Manager > for my wireless network), Network Manager does not automatically connect > to the network. I'm not sure why. No messages? Could it be that it fails to record settings? > I would love to see this patch go into master, but I have a few > concerns (which are probably non-blocking): > > * It looks like it's possible to have an "incomplete deployment" of > services in GuixSD. For example, if you add (e.g., > network-manager-service) without also adding wpa-supplicant-service, > the 'reconfigure' will succeed, but the wireless aspects of Network > Manager will not work. This seems undesirable. In the same way that > Guix/Nix ensures "complete deployment" of components in the store, is > there a way we can ensure complete deployment of services in GuixSD? Attempts to define a Shepherd service that depends on a undefined service leads to an error. So for example, if you have a =E2=80=98network-manager-service-type=E2=80= =99 instead but there is nothing defining a =E2=80=98wpa-supplicant=E2=80=99 Shepherd servi= ce, you get an error when running =E2=80=98guix system=E2=80=99. > * Should we update the desktop templates in > gnu/system/examples/desktop.tmpl? It looks like it's impossible to > add both wicd-service and network-manager-service to the same config > file. Therefore, perhaps we should supply a "gnome-desktop.tmpl" > example for those who want the GNOME desktop specifically? The > changes necessary to get Network Manager working with the > "desktop.tmpl" might not be easy for someone who is new to Guile. Once you have reported total success with Network Manager :-), we can certainly remove Wicd from =E2=80=98%desktop-services=E2=80=99 and add it i= nstead! > * I'm not sure (yet) how to investigate why Network Manager is failing > to automatically connect. If you have any ideas, please let me know. Most GNOME programs use GSettings to save their settings, and that has a tendency to not work if the schemas aren=E2=80=99t well aligned with the st= ars. So I would suggest running the NM application/applet from a terminal so you can see any warnings it spits out (or maybe they go to ~/.xsession-errors otherwise?), and see if that might be a problem. Perhaps the schema hypothesis doesn=E2=80=99t hold because network-manager-applet is already built with =E2=80=98glib-or-gtk-build-system=E2=80=99. Dunno. Thanks, Ludo=E2=80=99.