From: Ricardo Wurmus <rekado@elephly.net>
To: "Wiktor Żelazny" <wz@freeshell.de>
Cc: help-guix@gnu.org
Subject: Re: Guix segfaults, how do I roll back?
Date: Sat, 18 Dec 2021 17:01:58 +0100 [thread overview]
Message-ID: <87tuf5rjao.fsf@elephly.net> (raw)
In-Reply-To: <20211218133122.esmgogn7rhcrb7ag@wzguix>
Wiktor Żelazny <wz@freeshell.de> writes:
> I just ran `guix pull` and the upgraded guix is greeting me with
> Segmentation fault. How shall I proceed? Is it a good idea and is it
> safe to relink ~/.config/guix/current from
> /var/guix/profiles/per-user/$USERNAME/current-guix to the preceding
> profile?
You can use the previous Guix to roll back. Instead of using “guix”
just run
/var/guix/profiles/per-user/$USERNAME/current-guix-110-link/bin/guix
where the number corresponds to one before the current generation.
That said: a segfault is highly unusual. Make sure that LD_LIBRARY_PATH
is not set. (It forces potentially incompatible libraries to be loaded,
which is a good way to trigger segfaults due to ABI differences.)
--
Ricardo
next prev parent reply other threads:[~2021-12-18 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 13:31 Guix segfaults, how do I roll back? Wiktor Żelazny
2021-12-18 16:01 ` Ricardo Wurmus [this message]
2021-12-19 19:46 ` Wiktor Żelazny
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=87tuf5rjao.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=wz@freeshell.de \
/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.
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).