The GUI installer throws an error

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Jan
Owner
unassigned
Submitted by
Jan
Severity
normal
J
(address . bug-guix@gnu.org)
tvkprtjlzlkrwomzieth@apau
What I did:Ran guix system installer from a DVD.When the system started I switched to tty3 mounted a flash drive and a partition in folders I made in /mnt/.Then I unmounted these disks and removed folders.Then I tried installing the system without any DE/WM.The installer asked me what network something I want to have, I picked DHCP.Then installation failed - "failed to build openssh".It asked me if I want to try again, I pressed yes and the installer threw an error I attached below.Guix version: 1.0.1System: amd64 --Jan
Attachment: file
Attachment: file
Attachment: 1.jpg
Attachment: 2.jpg
Attachment: 3.jpg
L
L
Ludovic Courtès wrote on 25 Jul 2019 18:39
(name . Jan)(address . tona_kosmicznego_smiecia@interia.pl)(address . 36753@debbugs.gnu.org)
87o91it6fs.fsf@gnu.org
Hello Jan,

Jan <tona_kosmicznego_smiecia@interia.pl> skribis:

Toggle quote (9 lines)
> What I did:Ran guix system installer from a DVD.When the system
> started I switched to tty3 mounted a flash drive and a partition in
> folders I made in /mnt/.Then I unmounted these disks and removed
> folders.Then I tried installing the system without any DE/WM.The
> installer asked me what network something I want to have, I picked
> DHCP.Then installation failed - "failed to build openssh".It asked me
> if I want to try again, I pressed yes and the installer threw an error
> I attached below.Guix version: 1.0.1System: amd64 --Jan

This looks a lot like this bug:


In a nutshell, currently the installer cannot be restarted upon failure,
and this is why you got this ugly backtrace.

However, “failed to build openssh” looks like another failure worth
investigating. Do you have more info as to what happened exactly, what
was printed? Can you reproduce it? It would be great if you could post
a picture of the screen at that point.

Thanks,
Ludo’.
J
(address . bug-guix@gnu.org)
20190814135232.203452ee@kompiuter
Toggle quote (5 lines)
> However, “failed to build openssh” looks like another failure worth
> investigating. Do you have more info as to what happened exactly,
> what was printed? Can you reproduce it? It would be great if you
> could post a picture of the screen at that point.

Sorry for the delay, I had no free hard drive do test installation
again.
The thing that failed to build was openssl, not openssh. The error
message is "build of /gnu/store/long-sum-openssl-1.0.2p.drv failed".
What I did during the installation:
- whole disk with encryption
- tor, mozilla nss
- i3, xfce, enlightenment
And when the installer asked me if I want to continue without network
connection I plugged-in the ethernet cable.
J
(address . bug-guix@gnu.org)
20190815003001.5af31f4f@kompiuter
Okay I've figured out what causes openssl build to fail - continuing
installation without network connection. The installer told
me network connection is required to install the system correctly, but
I thought only packages will be outdated. Is it a bug?
L
L
Ludovic Courtès wrote on 22 Aug 2019 23:52
(name . Jan)(address . tona_kosmicznego_smiecia@interia.pl)(address . 36753@debbugs.gnu.org)
87lfvkj2bf.fsf@gnu.org
Hello,

Jan <tona_kosmicznego_smiecia@interia.pl> skribis:

Toggle quote (5 lines)
> Okay I've figured out what causes openssl build to fail - continuing
> installation without network connection. The installer told
> me network connection is required to install the system correctly, but
> I thought only packages will be outdated. Is it a bug?

Network connectivity is definitely required.

That you were able to continue without networking looks like a bug.
However, I just tried, and when networking is unavailable, I get the
“Connection error” box that only allows me to go back to the “Checking
connectivity” dialog; there’s no way to skip that AFAICS.

Or did you turn off networking after you had it on initially?

Thanks,
Ludo’.
J
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 36753@debbugs.gnu.org)
20190823020245.5b037a18@kompiuter
Toggle quote (5 lines)
> That you were able to continue without networking looks like a bug.
> However, I just tried, and when networking is unavailable, I get the
> “Connection error” box that only allows me to go back to the “Checking
> connectivity” dialog; there’s no way to skip that AFAICS.

Okay, I now know what *probably* have happened. My proprietary
motherboard - MSI PC Mate B350 tricked me - after updating the firmware
and enabling the "UEFI mode" instead of "UEFI or legacy BIOS" I got a
higher resolution and network started to work normally. Before enabling
it, the GUI installer couldn't find network connection itself, so I had
to manually configure network connection by using ifconfig and dhclient,
then I just followed the GUI installer, and it somehow let me continue
with or without networking.
Tried switching back to BIOS mode, but I can't reproduce the bug
anymore. None of this happens on my librebooted machine, tried hard to
break the installation :). Guess that's it, thanks for your time. I'm
probably going to sell this nonfree machine anyway.

Jan
L
L
Ludovic Courtès wrote on 23 Aug 2019 22:54
(name . Jan)(address . tona_kosmicznego_smiecia@interia.pl)(address . 36753@debbugs.gnu.org)
875zmn38ne.fsf@gnu.org
Hi,

Jan <tona_kosmicznego_smiecia@interia.pl> skribis:

Toggle quote (18 lines)
>> That you were able to continue without networking looks like a bug.
>> However, I just tried, and when networking is unavailable, I get the
>> “Connection error” box that only allows me to go back to the “Checking
>> connectivity” dialog; there’s no way to skip that AFAICS.
>
> Okay, I now know what *probably* have happened. My proprietary
> motherboard - MSI PC Mate B350 tricked me - after updating the firmware
> and enabling the "UEFI mode" instead of "UEFI or legacy BIOS" I got a
> higher resolution and network started to work normally. Before enabling
> it, the GUI installer couldn't find network connection itself, so I had
> to manually configure network connection by using ifconfig and dhclient,
> then I just followed the GUI installer, and it somehow let me continue
> with or without networking.
> Tried switching back to BIOS mode, but I can't reproduce the bug
> anymore. None of this happens on my librebooted machine, tried hard to
> break the installation :). Guess that's it, thanks for your time. I'm
> probably going to sell this nonfree machine anyway.

OK, thanks for explaining; closing the bug.

Ludo’.
L
L
Ludovic Courtès wrote on 23 Aug 2019 22:54
control message for bug #36753
(address . control@debbugs.gnu.org)
874l2738mv.fsf@gnu.org
tags 36753 notabug
close 36753
quit
?
Your comment

This issue is archived.

To comment on this conversation send an email to 36753@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 36753
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch