From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Mathieu Othacehe <m.othacehe@gmail.com>, 35941@debbugs.gnu.org
Subject: bug#35941: Newt installer failure when wifi name is #f
Date: Tue, 28 May 2019 11:46:17 +0200 [thread overview]
Message-ID: <87ef4ikj2u.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20190528111519.2fa1ec58@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
>> --8<---------------cut here---------------start------------->8---
>> @@ -108,7 +108,8 @@
>> (define-record-type* <service>
>> service make-service
>> service?
>> - (name service-name) ; string
>> + (name service-name
>> + (default ""))
>> (type service-type) ; string
>> (path service-path) ; string
>> (strength service-strength) ; integer
>> --8<---------------cut here---------------end--------------->8---
>
> How would that help? The default is only used if NAME is missing in the
> constructor call, right? Or is it also used if NAME is present but #f ?
Good point! I haven't tested, that was just a thought, but you are
right, it won't help.
>> Thoughts?
>
> Have you checked whether you can then still connect to that nameless Wifi?
Yes, I can connect manually, but I'm not connecting to the nameless Wifi
anyways.
To clarify, the installer fails to _list_ the wifi networks. So if one
network happens to not disclose the SSID (which is rather common), I
suspect that the installer will always fail.
> I think there are some "security" settings on Wifi routers that allow
> you to hide the SSID or something, so I guess that's how this problem
> sprung up.
Absolutely.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-05-28 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 8:59 bug#35941: Newt installer failure when wifi name is #f Pierre Neidhardt
2019-05-28 9:15 ` Danny Milosavljevic
2019-05-28 9:46 ` Pierre Neidhardt [this message]
2019-05-28 9:17 ` Mathieu Othacehe
2019-05-28 10:00 ` Pierre Neidhardt
2019-05-28 10:02 ` Pierre Neidhardt
2019-05-28 15:19 ` Ludovic Courtès
2019-05-28 17:51 ` Pierre Neidhardt
2019-05-29 7:50 ` Mathieu Othacehe
2019-05-29 9:03 ` Ludovic Courtès
2019-05-29 9:46 ` bug#35620: " Mathieu Othacehe
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=87ef4ikj2u.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=35941@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=m.othacehe@gmail.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 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).