From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: sirgazil <sirgazil@zoho.com>, 35550@debbugs.gnu.org
Subject: bug#35550: Installer: wpa_supplicant fails to start
Date: Mon, 6 May 2019 21:47:41 +0200 [thread overview]
Message-ID: <20190506194741.qm7uha4fomsngdga@pelzflorian.localdomain> (raw)
In-Reply-To: <87k1f4y23d.fsf@gnu.org>
On Mon, May 06, 2019 at 12:21:26AM +0200, Ludovic Courtès wrote:
> It’d be great if you could do some testing with the patch below. Then I
> guess we’ll push a Shepherd release with this fix.
>
The second patch (the one for Guix is the only one I have tested)
works fine on the system which always failed before since sometime
after 1.0.
One time wpa-supplicant worked fine but it had an error establishing
the internet connection, but I am quite certain it was an unrelated
hardware issue.
Regards,
Florian
next prev parent reply other threads:[~2019-05-06 19:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 19:31 bug#35550: Installer: wpa_supplicant fails to start Ludovic Courtès
2019-05-03 20:51 ` Ludovic Courtès
2019-05-04 15:28 ` Ludovic Courtès
2019-05-05 20:26 ` Ludovic Courtès
2019-05-05 22:21 ` Ludovic Courtès
2019-05-06 19:47 ` pelzflorian (Florian Pelz) [this message]
2019-05-07 7:53 ` Ludovic Courtès
2019-05-06 20:00 ` Danny Milosavljevic
2019-05-07 8:05 ` Ludovic Courtès
2019-05-08 14:32 ` Ludovic Courtès
2019-05-08 22:25 ` Ludovic Courtès
2019-05-09 6:46 ` pelzflorian (Florian Pelz)
2019-05-09 10:18 ` Ludovic Courtès
2019-05-11 18:13 ` Ludovic Courtès
2019-05-03 21:26 ` Ricardo Wurmus
2019-05-04 3:26 ` sirgazil
2019-05-04 12:49 ` Ludovic Courtès
2019-05-04 14:07 ` pelzflorian (Florian Pelz)
2019-05-04 15:32 ` Ludovic Courtès
2019-05-04 15:47 ` pelzflorian (Florian Pelz)
2019-05-04 21:14 ` Ludovic Courtès
2019-05-04 21:34 ` pelzflorian (Florian Pelz)
2019-05-05 16:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190506194741.qm7uha4fomsngdga@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=35550@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=sirgazil@zoho.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.