From: Mark H Weaver <mhw@netris.org>
To: Hugo Saavedra <hm@listen.systems>
Cc: 35622@debbugs.gnu.org
Subject: bug#35622: Ran into a bug in the new graphical installer on WiFi setup
Date: Tue, 07 May 2019 18:01:29 -0400 [thread overview]
Message-ID: <87sgtp3ovf.fsf@netris.org> (raw)
In-Reply-To: <CAMa8jQ7-oVhgcUdDPTu0d=MuSHd8xck-XJ_vM9Kvrv-v_MCtqA@mail.gmail.com> (Hugo Saavedra's message of "Tue, 7 May 2019 11:56:05 -0600")
Hi Hugo,
Hugo Saavedra <hm@listen.systems> writes:
> Thanks for your work on GuixSD. I was excited to try out the new
> graphical installer, but ran into a bug while setting up WiFi.
I'm sorry to hear it. Thanks very much for the report.
> I've uploaded photos of the stacktrace for you to take a look at. This
> is running on a Dell Inspiron 11 3000 series.
>
> https://imgur.com/a/qcwgNXr
From the backtrace, I see that 'string-null?' was applied to #f, and I
guess it was the 'string-null?' called from the 'wifi-services'
procedure in (gnu installer newt wifi), here:
(define (wifi-services)
"Return all the connman services of wifi type."
(let ((services (connman-services)))
(filter (lambda (service)
(and (string=? (service-type service) "wifi")
(not (string-null? (service-name service)))))
services)))
It seems that one of the services returned by (connman-services) had #f
as its 'service-name'. The backtrace includes a (truncated) display of
the service in question:
#<<service> name: #f type: "wifi" path: "wifi_4cbb58…>
Looking at 'connman-services', it appears that in this case, the 'keys',
as returned by 'parse-keys' in (gnu installer connman), did not have a
"Name" association, or else its right-hand side was #f.
It would be good if someone more familiar with this code would
investigate further.
Thanks,
Mark
next prev parent reply other threads:[~2019-05-07 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 17:56 bug#35622: Ran into a bug in the new graphical installer on WiFi setup Hugo Saavedra
2019-05-07 22:01 ` Mark H Weaver [this message]
2019-05-08 13:06 ` Ludovic Courtès
2019-05-08 15:21 ` Hugo Saavedra
2019-05-08 22:09 ` Ludovic Courtès
2019-05-08 22: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=87sgtp3ovf.fsf@netris.org \
--to=mhw@netris.org \
--cc=35622@debbugs.gnu.org \
--cc=hm@listen.systems \
/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).