all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>
To: Roland Everaert <r.everaert@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: Foreign Distribution - how to disable guix home configuration?
Date: Tue, 29 Mar 2022 13:31:43 +0200	[thread overview]
Message-ID: <87zgl9hu5c.fsf@ruhr-uni-bochum.de> (raw)
In-Reply-To: <cnh5_0mptgCYa-UEk1ZNW4cR-NxwZa6PA-oQlS3AjOdv1OYCyhn9hYzLvL2TJptTyptSoU0sjnXX4SZe1QE_pfWUwMr2HBbftZPshzUJz1g=@protonmail.com> (Roland Everaert via's message of "Mon, 28 Mar 2022 16:30:27 +0000")

Hi Roland, hello Guix,

Roland Everaert via <help-guix@gnu.org> writes:

> Since I have updated my fedora box from version 34 to version 35, the
> libry path is messed up and most applications installed via dnf
> (fedora package manager) does not run.
>
> In a terminal (only xterm works so far), starting one of those failing
> application output a symbol lookup error with a path to a library in
> the /gnu/store, so far I only see reference to libpthread.
>
> I suspect guix home to be the culprit, so, I would like to ensure it
> is not started, to confirm or not my suspition.
>
> So, what is the best way to disable/deactivate it?

IIUC your ~/.profile should contain something like:

--8<---------------cut here---------------start------------->8---
HOME_ENVIRONMENT=$HOME/.guix-home
. $HOME_ENVIRONMENT/setup-environment
$HOME_ENVIRONMENT/on-first-login
--8<---------------cut here---------------end--------------->8---

So the way to ‘deactivate’ guix home would be to delete these lines as
these are run during login.

Best

-- 
Daniel


      reply	other threads:[~2022-03-29 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 16:30 Foreign Distribution - how to disable guix home configuration? Roland Everaert via
2022-03-29 11:31 ` Daniel Meißner [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgl9hu5c.fsf@ruhr-uni-bochum.de \
    --to=daniel.meissner-i4k@ruhr-uni-bochum.de \
    --cc=help-guix@gnu.org \
    --cc=r.everaert@protonmail.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.