unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Wiktor Żelazny" <wz@freeshell.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Guix segfaults, how do I roll back?
Date: Sun, 19 Dec 2021 20:46:42 +0100	[thread overview]
Message-ID: <20211219194642.45xbslm2sgt4xxom@wzguix> (raw)
In-Reply-To: <87tuf5rjao.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]

On Sat, Dec 18, 2021 at 05:01:58PM +0100, Ricardo Wurmus wrote:

> just run
> /var/guix/profiles/per-user/$USERNAME/current-guix-110-link/bin/guix

Thank you, Ricardo, for this simple solution.

> Make sure that LD_LIBRARY_PATH is not set.

It is set, but after `unset LD_LIBRARY_PATH` Guix keeps segfaulting.
However, this

   $ /var/guix/profiles/per-user/$USERNAME/current-guix-152-link/bin/guix shell -C guix -- guix --version
   guix (GNU Guix) 1.3.0-13.8cc099b
   Copyright (C) 2021 the Guix authors
   License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
   This is free software: you are free to change and redistribute it.
   There is NO WARRANTY, to the extent permitted by law.

works, and returns a newer commit than

   $ /var/guix/profiles/per-user/$USERNAME/current-guix-152-link/bin/guix --version
   guix (GNU Guix) b3a801330ed1c126a215fa8e3ff2aea0880eeba8
   Copyright (C) 2021 the Guix authors
   License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
   This is free software: you are free to change and redistribute it.
   There is NO WARRANTY, to the extent permitted by law.

, so I assume that it is the new Guix, without a segfault when in a
container.

WŻ

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

      reply	other threads:[~2021-12-19 19:47 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
2021-12-19 19:46   ` Wiktor Żelazny [this message]

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=20211219194642.45xbslm2sgt4xxom@wzguix \
    --to=wz@freeshell.de \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).