From: Timothy Sample <samplet@ngyro.com>
To: Jonathan Frederickson <jonathan@terracrypt.net>
Cc: help-guix@gnu.org
Subject: Re: Setting environment variables in Gnome session
Date: Wed, 28 Aug 2019 20:40:07 -0400 [thread overview]
Message-ID: <87ef14pzx4.fsf@ngyro.com> (raw)
In-Reply-To: <20190828155348.5dbe862c@terracrypt.net> (Jonathan Frederickson's message of "Wed, 28 Aug 2019 15:53:48 -0400")
Hi Jonathan,
Jonathan Frederickson <jonathan@terracrypt.net> writes:
> I'm trying to install some software through Flatpak alongside software
> installed through Guix (on a Guix System install) and I'm running into
> what feels like it should be a minor issue. On other distros (including
> my desktop where I'm running Guix as a foreign package manager), I
> would modify XDG_DATA_DIRS in $HOME/.profile to accomplish this.
>
> However, my Gnome session in Guix System seems to ignore this file.
> I've tried creating a file in my home directory in /etc/profile like
> so, and as far as I can tell it's never getting run:
>
> export XDG_DATA_DIRS=$XDG_DATA_DIRS:/var/lib/flatpak/exports/share
> echo "hi there!" > $HOME/test.txt
>
> Is there a preferred way to set environment variables in a graphical
> session?
If you use GDM and GNOME, and have Bash as your shell, you need to set
the variables in “~/.bash_profile” or “~/.bashrc”. Guix System sets up
GDM to run your X session from the your login shell (which I’m assuming
is Bash). Since Guix System provides a “~/.bash_profile” file by
default, Bash will read this and skip “~/.profile”.
So if you set the variables in a Bash-specific file it should work.
-- Tim
next prev parent reply other threads:[~2019-08-29 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 19:53 Setting environment variables in Gnome session Jonathan Frederickson
2019-08-28 20:58 ` Jonathan Frederickson
2019-08-29 0:40 ` Timothy Sample [this message]
2019-08-29 0:50 ` Jonathan Frederickson
2019-08-29 1:15 ` Timothy Sample
2019-08-29 4:06 ` Jonathan Frederickson
2019-08-29 3:03 ` Jesse Gibbons
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=87ef14pzx4.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=help-guix@gnu.org \
--cc=jonathan@terracrypt.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).