From: Leo Famulari <leo@famulari.name>
To: bdju <bdju@tilde.team>
Cc: 53541@debbugs.gnu.org
Subject: bug#53541: backtrace during fresh Guix System install after during formatting
Date: Thu, 3 Feb 2022 23:15:53 -0500 [thread overview]
Message-ID: <Yfyoecw+Xnqqfxvm@jasmine.lan> (raw)
In-Reply-To: <CHMY3I6N3QUY.3GZRXDZ9RY6YR@masaki>
On Thu, Feb 03, 2022 at 09:34:11PM -0600, bdju wrote:
> It would be difficult to test now, I no longer have an empty SSD waiting
> to be installed on in the same PC.
Understood.
> I ended up getting through an install
> with the last stable release using the same settings.
> From memory, it was set up for EFI, btrfs root partition, encryption
> enabled, boot partition was fat32, I chose no environment (wanted to use
> sway), accepted networkmanager, tor, cups... I kept the default
> generated config.scm because it often crashed when trying to edit and I
> was sick of starting over. I think the crash was either right before the
> screen where you can edit the config or right after you tell it to apply
> the config.
Okay. The crash when you do edit the config has been fixed, based on our
testing:
https://issues.guix.gnu.org/53544
I know this report was about a different issue, but not as clearly
defined.
> I had a second HDD (not touched by the installer) in
> addition to the SSD being installed on, and /dev/sdc/ was the flash
> drive with the installer image on it.
> I am glad to hear it's (maybe) fixed. I'll download a new ISO, but I
> don't have a hypervisor configured to test this sort of thing. I could
> maybe try it with a different computer, but still it would be hard to
> find one I'm willing to wipe I think. Sorry I can't be more help.
> I have still only ever done 3 full Guix System installs, all years
> apart. Unfortunately I never considered the experience fun enough to do
> besides when absolutely necessary.
No worries! You already helped a lot by reporting the bug and giving us
all the details you can. I will do some tests in a VM, choosing
non-default filesystems and partitioning.
next prev parent reply other threads:[~2022-02-04 4:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 3:21 bug#53541: backtrace during fresh Guix System install after during formatting bdju via Bug reports for GNU Guix
2022-01-26 3:42 ` bug#53541: backtrace during fresh Guix System install " bdju via Bug reports for GNU Guix
2022-01-26 4:08 ` bdju via Bug reports for GNU Guix
2022-01-26 4:14 ` bdju via Bug reports for GNU Guix
2022-02-03 18:34 ` bug#53541: backtrace during fresh Guix System install after " Leo Famulari
2022-02-04 3:34 ` bdju via Bug reports for GNU Guix
2022-02-04 4:15 ` Leo Famulari [this message]
[not found] ` <877d0uebt9.fsf_-_@gnu.org>
2022-10-22 17:00 ` bug#53541: [installer] " Mathieu Othacehe
2022-10-22 20:34 ` Mathieu Othacehe
2022-10-31 8:35 ` 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=Yfyoecw+Xnqqfxvm@jasmine.lan \
--to=leo@famulari.name \
--cc=53541@debbugs.gnu.org \
--cc=bdju@tilde.team \
/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).