From mboxrd@z Thu Jan 1 00:00:00 1970 From: "pelzflorian (Florian Pelz)" Subject: bug#35550: Installer: wpa_supplicant fails to start Date: Sat, 4 May 2019 16:07:54 +0200 Message-ID: <20190504140753.6wjgctw6ird7xj2b@pelzflorian.localdomain> References: <87sgtv8hcz.fsf@gnu.org> <16a80e1461c.1292821a927951.2710363725930741694@zoho.com> <87k1f64c5o.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:49389) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hMvLb-0001Ys-Rg for bug-guix@gnu.org; Sat, 04 May 2019 10:09:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hMvLa-0006wd-Q0 for bug-guix@gnu.org; Sat, 04 May 2019 10:09:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:38373) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hMvLa-0006wS-MI for bug-guix@gnu.org; Sat, 04 May 2019 10:09:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hMvLa-0006jV-9F for bug-guix@gnu.org; Sat, 04 May 2019 10:09:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87k1f64c5o.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: sirgazil@zoho.com, 35550 <35550@debbugs.gnu.org> On Sat, May 04, 2019 at 02:49:55PM +0200, Ludovic Courtès wrote: > 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? > So for me it sometimes fails on two different machines. Actually it started failing four times in a row now that I test this. When it fails, I also get On Fri, May 03, 2019 at 09:31:40PM +0200, Ludovic Courtès wrote: > 680 May 3 16:03:40 localhost wpa_supplicant[398]: Successfully initialized wpa_supplicant > 681 May 3 16:03:40 localhost shepherd[1]: Service wpa-supplicant could not be started. > 682 May 3 16:03:40 localhost shepherd[1]: Service networking depends on wpa-supplicant. > 683 May 3 16:03:40 localhost shepherd[1]: Service networking could not be started. > 684 May 3 16:03:40 localhost wpa_supplicant[400]: dbus: Could not request service name: already registered > 685 May 3 16:03:40 localhost wpa_supplicant[400]: Failed to initialize wpa_supplicant > 686 May 3 16:03:45 localhost shepherd[1]: Service wpa-supplicant could not be started. > Could you also: > > 1. Let the installation image boot; > > 2. Confirm with ‘herd status wpa-supplicant’ that the ‘wpa-supplicant’ > service is marked as stopped (failed to start); > $ herd status wpa-supplicant Status of wpa-supplicant: It is stopped. It is enabled. Provides (wpa-supplicant). Requires (user-processes dbus-system loopback syslogd). Conflicts with (). Will be respawned. > 3. Show the contents /var/run/wpa_supplicant.pid, and check whether > they correspond to the PID of a running ‘wpa_supplicant’ process. > There is no such file. Regards, Florian