[installer] Trying to edit the generated config.scm crashes the installer

  • Done
  • quality assurance status badge
Details
2 participants
  • Leo Famulari
  • Mathieu Othacehe
Owner
unassigned
Submitted by
Leo Famulari
Severity
normal
L
L
Leo Famulari wrote on 26 Jan 2022 05:14
(address . bug-guix@gnu.org)
YfDKvOlAVFQyt3rf@jasmine.lan
While testing the installer built from the current master branch, we
found that trying to edit the generated config.scm crashes the
installer. Screenshot attached.

I built the installer like this:

$ guix environment guix -- ./pre-inst-env guix system image -t uncompressed-iso9660 --label="GUIX_x86_64-linux-leo" --system=x86_64-linux gnu/system/install.scm

I created a disk to install it with QEMU:

$ qemu-img create -f qcow2 guix-system.img 50G

And I ran the installer like this:

$ qemu-system-x86_64 -m 1024 -smp 1 -enable-kvm -nic user,model=virtio-net-pci -boot menu=on,order=d -device virtio-blk,drive=myhd -drive if=none,file=guix-system.img,id=myhd -drive media=cdrom,file=my-image.iso

I proceeded to select the default answers for all questions: no desktop,
the default networking-related services, DHCP network provider, guided
partitioning using the entire disk.

At the end, it shows the generated configuration, and crashes when I
select "edit". Unfortunately, the installer becomes unresponsive when
this happens, so I cannot scroll down and read the entire backtrace.
L
L
Leo Famulari wrote on 26 Jan 2022 05:18
(no subject)
(address . control@debbugs.gnu.org)
YfDLfRicGkaiLTJL@jasmine.lan
block 53214 with 53544
block 53214 with 53541
M
M
Mathieu Othacehe wrote on 2 Feb 2022 18:23
Re: bug#53544: [installer] Trying to edit the generated config.scm crashes the installer
(name . Leo Famulari)(address . leo@famulari.name)(address . 53544-done@debbugs.gnu.org)
87czk5chdz.fsf@gnu.org
Hello Leo,

Toggle quote (4 lines)
> At the end, it shows the generated configuration, and crashes when I
> select "edit". Unfortunately, the installer becomes unresponsive when
> this happens, so I cannot scroll down and read the entire backtrace.

I followed the exact same steps on Guix commit
4943ac86e4f95a2e14fd209f3fdaac74a0d9ca2e and could not reproduce the
issue. It was possibly fixed by the wip-harden-installer branch
merge. Could you please confirm that you have the same behaviour
locally?

Thanks,

Mathieu
Closed
L
L
Leo Famulari wrote on 2 Feb 2022 20:08
(name . Mathieu Othacehe)(address . othacehe@gnu.org)(address . 53544-done@debbugs.gnu.org)
YfrWoQycA/E5I3b/@jasmine.lan
On Wed, Feb 02, 2022 at 06:23:04PM +0100, Mathieu Othacehe wrote:
Toggle quote (6 lines)
> I followed the exact same steps on Guix commit
> 4943ac86e4f95a2e14fd209f3fdaac74a0d9ca2e and could not reproduce the
> issue. It was possibly fixed by the wip-harden-installer branch
> merge. Could you please confirm that you have the same behaviour
> locally?

Indeed, it must have been fixed by the recent changes from that branch.
Thanks!
Closed
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 53544
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