From debbugs-submit-bounces@debbugs.gnu.org Tue Apr 09 20:09:35 2019 Received: (at 34991) by debbugs.gnu.org; 10 Apr 2019 00:09:35 +0000 Received: from localhost ([127.0.0.1]:52187 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hE0o3-0007TB-8A for submit@debbugs.gnu.org; Tue, 09 Apr 2019 20:09:35 -0400 Received: from mx1.riseup.net ([198.252.153.129]:60280) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hE0o1-0007T3-Dx for 34991@debbugs.gnu.org; Tue, 09 Apr 2019 20:09:34 -0400 Received: from capuchin.riseup.net (capuchin-pn.riseup.net [10.0.1.176]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 8F2EF1A3EDC for <34991@debbugs.gnu.org>; Tue, 9 Apr 2019 17:09:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1554854972; bh=jVoX8bfxGGuWn/xIXHn0IXL6IxQ4tcKOwXQnmVKjc+0=; h=Date:From:To:Subject:In-Reply-To:References:From; b=CwO+CfYnIgcXkziBAsBXreNlEbmcUrkTEPgnJLR6pbrYpD6JtCGq/JmBZw/CE5xEA fXR7II/hX5X42udfTg+bWf9y9RTa+/v32JVg9ua509TE27UwNgI7wXfvutZVni4F6s REEuxW9+U08F35P264t+Q2gkDoJA5agANdbsUHmI= X-Riseup-User-ID: 5440029044B74A862CA4422771C0C4CA4E6C6CABA8DE41454B106D118619C592 Received: from [127.0.0.1] (localhost [127.0.0.1]) by capuchin.riseup.net (Postfix) with ESMTPSA id 7010912031A for <34991@debbugs.gnu.org>; Tue, 9 Apr 2019 17:09:32 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: Tue, 09 Apr 2019 17:09:32 -0700 From: Quiliro Ordonez To: 34991@debbugs.gnu.org Subject: Re: bug#34991: network manager error with wireless card when wired card connected In-Reply-To: <432a41012feae80c4967d97180c5b2fb@riseup.net> References: <55b32fcde217f16b09d1398dfc478d8f@riseup.net> <87lg0qojw0.fsf@gnu.org> <32c8ad168a757fcc3f63ef158a0d3360@riseup.net> <878swqurrj.fsf@gnu.org> <432a41012feae80c4967d97180c5b2fb@riseup.net> Message-ID: <2b50bb496027a0d0d5fa7ca6d45d0bad@riseup.net> X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 34991 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) El 2019-04-04 17:35, Quiliro Ordonez escribió: > El 2019-04-04 07:57, Ludovic Courtès escribió: >> Hola, >> >> Quiliro Ordonez skribis: >> >>> El 2019-04-03 21:31, Ludovic Courtès escribió: >>>> Hi Quiliro, >>>> >>>> Quiliro Ordonez skribis: >>>> >>>>> When i install my PCI wireless card and my ethernet card is plugged to >>>>> its cable, network manager fails to start because of an error starting >>>>> wpa_supplicant. >>>> >>>> Could you provide the actual error messages that you see? You can >>>> hopefully get them from /var/log/messages. >>>> >>>> Without that information there’s nothing we can do about the issue. >>> >>> I cannot see anything else on the log. I attach the respective file. >>> >>> Also, i tryed restarting the networking service: >>> ~$ sudo herd restart networking >>> Service networking is not running. >>> Service wpa-supplicant could not be started. >>> Service networking depends on wpa-supplicant. >>> Service networking could not be started. >> >> Indeed, the log is unhelpful. When you run this command, is there >> anything that gets printed on the console? (You can hit ctrl-alt-f1 and >> then run ’sudo herd start wpa-supplicant’ from there.) > > Right now the networking service has started normally. This error > starting networking service is a situation that is present sometimes on > boot and others it is not. When it is present, I run: > sudo iwconfig wlp2s1 essid QO > sudo dhclient wlp2s1 -v > After that, can connect to the network. I can also make the test you > ask. I did it before. I do not remember exactly the error message when > trying: > sudo herd restart wpa-supplicant > But I do remember that there was no information that told baout the > problem except that it was unable to start it. The log which I sont on > the previous message said that it could not start wpa-supplicant because > it depended on dbus-system. But I when I restarted that service, the > machine became unusable; probably because the login manager stopped > working and I had to restart the machine. > > HH!, > Quiliro. I have no problem since the message above. Posibly because a new Guix commit fixed it after which I pulled and reconfigured.