unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Quiliro Ordonez <quiliro@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34991@debbugs.gnu.org
Subject: bug#34991: network manager error with wireless card when wired card connected
Date: Thu, 04 Apr 2019 10:35:02 -0700	[thread overview]
Message-ID: <432a41012feae80c4967d97180c5b2fb@riseup.net> (raw)
In-Reply-To: <878swqurrj.fsf@gnu.org>

El 2019-04-04 07:57, Ludovic Courtès escribió:
> Hola,
> 
> Quiliro Ordonez <quiliro@riseup.net> skribis:
> 
>> El 2019-04-03 21:31, Ludovic Courtès escribió:
>>> Hi Quiliro,
>>>
>>> Quiliro Ordonez <quiliro@riseup.net> 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.

  reply	other threads:[~2019-04-04 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25  7:44 bug#34991: network manager error with wireless card when wired card connected Quiliro Ordonez
2019-04-03 21:31 ` Ludovic Courtès
2019-04-04  0:57   ` Quiliro Ordonez
2019-04-04  7:57     ` Ludovic Courtès
2019-04-04 17:35       ` Quiliro Ordonez [this message]
2019-04-10  0:09         ` Quiliro Ordonez
2019-04-03 21:32 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=432a41012feae80c4967d97180c5b2fb@riseup.net \
    --to=quiliro@riseup.net \
    --cc=34991@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).