From: Hugo Saavedra <hm@listen.systems>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35622@debbugs.gnu.org
Subject: bug#35622: Ran into a bug in the new graphical installer on WiFi setup
Date: Wed, 8 May 2019 09:21:21 -0600 [thread overview]
Message-ID: <CAMa8jQ7uCviRubpr=0ayCbN3T9D5RE5EtU+sg+pFyHvADyOzsA@mail.gmail.com> (raw)
In-Reply-To: <87k1f1w0wh.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Sorry about that -- I just posted them on my own server here
https://topologi.es/files/d/5e38edf49f744b099d70/?p=/&mode=grid
On Wed, May 8, 2019 at 7:07 AM Ludovic Courtès <ludo@gnu.org> wrote:
> Hello,
>
> Mark H Weaver <mhw@netris.org> skribis:
>
> > 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:
>
> Could you post the image here? imgur.com says it’s “over capacity” and
> I can’t see the image right now.
>
> Ludo’.
>
--
*Hugo Saavedra*
Listen Systems <http://listen.systems>
c: 818-356-6664
<http://listen.systems>
[-- Attachment #2: Type: text/html, Size: 2939 bytes --]
next prev parent reply other threads:[~2019-05-08 15:52 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
2019-05-08 13:06 ` Ludovic Courtès
2019-05-08 15:21 ` Hugo Saavedra [this message]
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='CAMa8jQ7uCviRubpr=0ayCbN3T9D5RE5EtU+sg+pFyHvADyOzsA@mail.gmail.com' \
--to=hm@listen.systems \
--cc=35622@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).