unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andrews, Kyle (KC)" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "60141@debbugs.gnu.org" <60141@debbugs.gnu.org>
Subject: bug#60141: Follow-up
Date: Fri, 13 Jan 2023 16:43:47 +0000	[thread overview]
Message-ID: <SA0P164MB0151B283F9A4515D1998D040B9C29@SA0P164MB0151.NAMP164.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <SJ0P164MB01453403CC361A06CB245829B9FD9@SJ0P164MB0145.NAMP164.PROD.OUTLOOK.COM>

My system administrator let me know that the terminal I was presented with was sandboxed by RStudio Server (not running on Guix) and that this was responsible for causing the error.

I was able to run the hello command from an unsandboxed shell. I was also able to pull the latest version of guix using the same method.


General Business

-----Original Message-----
From: Andrews, Kyle (KC) 
Sent: Thursday, January 12, 2023 5:28 PM
To: 60141@debbugs.gnu.org
Subject: Follow-up

I moved .config/guix to .config/guix.bkp and that allowed me to execute the basic guix 1.3.0 commands again. However, whatever I create the result is always the same. I get segmentation fault (core dumped). For example:

$ guix install hello
$ {{source the profile}}
$ hello
Segmentation fault (core dumped)

General Business




  reply	other threads:[~2023-01-13 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 17:15 bug#60141: Stack smashing detected after first guix pull on fresh Ubuntu 22.04 guix install Andrews, Kyle (KC) via Bug reports for GNU Guix
2023-01-12 22:27 ` bug#60141: Follow-up Andrews, Kyle (KC) via Bug reports for GNU Guix
2023-01-13 16:43   ` Andrews, Kyle (KC) via Bug reports for GNU Guix [this message]
2023-01-17 15:20     ` bug#60141: Stack smashing detected after first guix pull on fresh Ubuntu 22.04 guix install Ludovic Courtès

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=SA0P164MB0151B283F9A4515D1998D040B9C29@SA0P164MB0151.NAMP164.PROD.OUTLOOK.COM \
    --to=bug-guix@gnu.org \
    --cc=60141@debbugs.gnu.org \
    --cc=KCAndrews@dow.com \
    /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).