From: Martin Castillo <castilma@uni-bremen.de>
To: help-guix@gnu.org
Subject: Re: Help-Guix Digest, Vol 89, Issue 35
Date: Thu, 20 Apr 2023 16:20:10 +0200 [thread overview]
Message-ID: <6b38f4c7-7a29-a7a7-0116-ed404c0dff48@uni-bremen.de> (raw)
In-Reply-To: <17b5be08-2429-337f-8eb8-ea36e484a12d@posteo.de>
Hi,
Am 20.04.23 um 14:52 schrieb Gottfried:
> Hi,
>
> gfp@Tuxedo ~$ ps $(ps -p $(pidof Xorg) -o ppid=)
> PID TTY STAT TIME COMMAND
> 1114 tty8 Ssl+ 0:00
> /gnu/store/58hc6rh72z3r6zqazmavjnwbcyy6gkps-gdm-42.0/libexec/gd
>
> it shows gdm-42.0 as my display manager
> ..........................................................................
>> A quick search makes me think gdm sources .xprofile. So adding
>>> source ~/.bash_profile
>>> to ~/.xprofile should work.
>
> this is in my .zprofile file, after adding the second sentence/your
> proposal
>
> # Honor system-wide environment variables
> source /etc/profile
> # all Profile beim Start des Displays Managers öffnen
> source ~/.bash_profile
> ..........................................................................
>
> but it didn’t help to enable all profiles at login.
Ok, I can think of 2 potential problems. 1) xprofile is not read on
login or 2) something is wrong with the lines in .bash_profile that
should activate the profiles.
To test 1) add
echo reading xprofile on $(date) >>~/login.log
to your .xprofile and logout and back in.
If this file is really sourced on login, you should find the file
~/login.log with a line saying something like reading xprofile on Do 20.
Apr 16:13:21 CEST 2023.
If login.log does not exist, then maybe ~/.xprofile is not executable?
Try chmod +x ~/.xprofile and re-login.
If login.log exists, then there seems to be something wrong with the
lines that should activate the profiles in .bash_profile.
To test 2) start a login shell with a clean environment
env - bash -l
and check whether that shell has all the profiles activated. If not,
there is something wrong with your .bash_profile. You should post that then.
Martin
next prev parent reply other threads:[~2023-04-20 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2930.1681985495.30476.help-guix@gnu.org>
2023-04-20 12:52 ` Help-Guix Digest, Vol 89, Issue 35 Gottfried
2023-04-20 14:20 ` Martin Castillo [this message]
2023-04-20 14:22 ` Martin Castillo
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=6b38f4c7-7a29-a7a7-0116-ed404c0dff48@uni-bremen.de \
--to=castilma@uni-bremen.de \
--cc=help-guix@gnu.org \
/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).