From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#35550: Installer: wpa_supplicant fails to start Date: Sat, 04 May 2019 14:49:55 +0200 Message-ID: <87k1f64c5o.fsf@gnu.org> References: <87sgtv8hcz.fsf@gnu.org> <16a80e1461c.1292821a927951.2710363725930741694@zoho.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:60630) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMu87-000375-6z for bug-guix@gnu.org; Sat, 04 May 2019 08:51:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMu86-0003Z2-BJ for bug-guix@gnu.org; Sat, 04 May 2019 08:51:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37002) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hMu86-0003Ys-7E for bug-guix@gnu.org; Sat, 04 May 2019 08:51:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hMu86-0004V3-0n for bug-guix@gnu.org; Sat, 04 May 2019 08:51:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <16a80e1461c.1292821a927951.2710363725930741694@zoho.com> (sirgazil@zoho.com's message of "Fri, 03 May 2019 22:26:48 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: sirgazil@zoho.com Cc: 35550 <35550@debbugs.gnu.org> Hi, sirgazil@zoho.com skribis: > In my case, "wpa-supplicant" would *always* fail to start (I rebooted and= tried the graphical installer around 4 times). Could you check whether the sequence of events in /var/log/messages always looks like the snippet I showed? Could you also: 1. Let the installation image boot; 2. Confirm with =E2=80=98herd status wpa-supplicant=E2=80=99 that the =E2= =80=98wpa-supplicant=E2=80=99 service is marked as stopped (failed to start); 3. Show the contents /var/run/wpa_supplicant.pid, and check whether they correspond to the PID of a running =E2=80=98wpa_supplicant=E2=80= =99 process. ? Besides, do you have a Guix(SD) installation, recent or not, that uses wpa_supplicant? If so, does it suffer from the same problem (=E2=80=98wpa-supplicant=E2=80=99 service fails to start)? Thanks, Ludo=E2=80=99.