Re: Help-Guix Digest, Vol 89, Issue 35 (Martin Castillo)

Re: Help-Guix Digest, Vol 89, Issue 35 (Martin Castillo)

[Gottfried]

[-- Attachment #1.1.1: Type: text/plain, Size: 7185 bytes --]

Hi,

thanks for help.

1.
> To test 1) add
>> echo reading xprofile on $(date) >>~/login.log
>> to your .xprofile and logout and back in.

I have a file .zprofile in my home directory
but not a file: .xprofile

I tried with both to add it to my .zprofile file
did not help.

---------------------------------------------------------

2.
> 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.

I did not find a file: ~/login.log

I have  files:
.e-log.log
.e-log.log.old

or they are in a different directory?

------------------------------------------------------------------
in /etc/profile there is:

# Crucial variables that could be missing in the profiles' 'etc/profile'
# because they would require combining both profiles.
# FIXME: See <http://bugs.gnu.org/20255>.
export 
MANPATH=$HOME/.guix-profile/share/man:/run/current-system/profile/share/man
export 
INFOPATH=$HOME/.guix-profile/share/info:/run/current-system/profile/share/info
export 
XDG_DATA_DIRS=$HOME/.guix-profile/share:/run/current-system/profile/share
export 
XDG_CONFIG_DIRS=$HOME/.guix-profile/etc/xdg:/run/current-system/profile/etc/xdg

# Make sure libXcursor finds cursors installed into user or system 
profiles.  See <http://bugs.gnu.org/24445>
export 
XCURSOR_PATH=$HOME/.icons:$HOME/.guix-profile/share/icons:/run/current-system/profile/share/icons

# Ignore the default value of 'PATH'.
unset PATH

# Load the system profile's settings.
GUIX_PROFILE=/run/current-system/profile ; \
. /run/current-system/profile/etc/profile

# Since 'lshd' does not use pam_env, /etc/environment must be explicitly
# loaded when someone logs in via SSH.  See <http://bugs.gnu.org/22175>.
# We need 'PATH' to be defined here, for 'cat' and 'cut'.  Do this before
# reading the user's 'etc/profile' to allow variables to be overridden.
if [ -f /etc/environment -a -n "$SSH_CLIENT" \
       -a -z "$LINUX_MODULE_DIRECTORY" ]
then
    . /etc/environment
    export `cat /etc/environment | cut -d= -f1`
fi

# Arrange so that ~/.config/guix/current comes first.
for profile in "$HOME/.guix-profile" "$HOME/.config/guix/current"
do
    if [ -f "$profile/etc/profile" ]
    then
      # Load the user profile's settings.
      GUIX_PROFILE="$profile" ; \
      . "$profile/etc/profile"
    else
      # At least define this one so that basic things just work
      # when the user installs their first package.
      export PATH="$profile/bin:$PATH"
    fi
done

# Prepend setuid programs.
export PATH=/run/setuid-programs:$PATH

# Arrange so that ~/.config/guix/current/share/info comes first.
export INFOPATH="$HOME/.config/guix/current/share/info:$INFOPATH"

# Set the umask, notably for users logging in via 'lsh'.
# See <http://bugs.gnu.org/22650>.
umask 022

# Allow Hunspell-based applications (IceCat, LibreOffice, etc.) to
# find dictionaries.
export 
DICPATH="$HOME/.guix-profile/share/hunspell:/run/current-system/profile/share/hunspell"

# Allow GStreamer-based applications to find plugins.
export GST_PLUGIN_PATH="$HOME/.guix-profile/lib/gstreamer-1.0"

if [ -n "$BASH_VERSION" -a -f /etc/bashrc ]
then
    # Load Bash-specific initialization code.
    . /etc/bashrc
fi


I don’t know if that helps, so I copied it
----------------------------------------------------------------------

3.
> Try chmod +x ~/.xprofile and re-login.

gfp@Tuxedo ~$ chmod +x ~/.xprofile
chmod: Zugriff auf '/home/gfp/.xprofile' nicht möglich: Datei oder 
Verzeichnis nicht gefunden

If I do a:
gfp@Tuxedo ~$ chmod +x ~/.zprofile
gfp@Tuxedo ~$

something was done.




-------------------------------------------------------------------
> 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.


gfp@Tuxedo ~$ env - $(which bash) -l
gfp@Tuxedo /home/gfp$ icecat
Error: no DISPLAY environment variable specified
gfp@Tuxedo /home/gfp$ chromium
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
Fontconfig error: No writable cache directories
[7535:7535:0422/182050.365759:ERROR:ozone_platform_x11.cc(238)] Missing 
X server or $DISPLAY
[7535:7535:0422/182050.366270:ERROR:env.cc(255)] The platform failed to 
initialize.  Exiting.
gfp@Tuxedo /home/gfp$

I tried to open icecat and chromium in that shell but it doesn’t work.

hopefully we are one step further

Kind regards

Gottfried


> Message: 5
> Date: Thu, 20 Apr 2023 16:20:10 +0200
> From: Martin Castillo <castilma@uni-bremen.de>
> To: help-guix@gnu.org
> Subject: Re: Help-Guix Digest, Vol 89, Issue 35
> Message-ID: <6b38f4c7-7a29-a7a7-0116-ed404c0dff48@uni-bremen.de>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> 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









[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: Help-Guix Digest, Vol 89, Issue 35 (Martin Castillo)

[Martin Castillo]

Hi,

Am 22.04.23 um 18:25 schrieb Gottfried:
> Hi,
> 
> thanks for help.
> 
> 1.
>> To test 1) add
>>> echo reading xprofile on $(date) >>~/login.log
>>> to your .xprofile and logout and back in.
> 
> I have a file .zprofile in my home directory
> but not a file: .xprofile
> 

I thought it was a typo in your other mail. zprofile is the startup file 
for the zsh shell. It's corresponds to the .bash_profile for bash.

But I really mean .xprofile. If it does not exist, create the file and write

# all Profile beim Start des Displays Managers öffnen
source ~/.bash_profile

into it.
Also, remove that line from the zprofile.

> I tried with both to add it to my .zprofile file
> did not help.
> 
> ---------------------------------------------------------
> 
> 2.
>> 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.
> 
> I did not find a file: ~/login.log
> 
> I have  files:
> .e-log.log
> .e-log.log.old
> 
> or they are in a different directory?
> 

Try again after doing what I wrote above.

> ------------------------------------------------------------------
> in /etc/profile there is > I don’t know if that helps, so I copied it
No, it does not. Unless you changed it in your system config, it's the 
same every other guix user has on their system.


> -------------------------------------------------------------------
>> 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.
> 
> 
> gfp@Tuxedo ~$ env - $(which bash) -l
> gfp@Tuxedo /home/gfp$ icecat
> Error: no DISPLAY environment variable specified
> gfp@Tuxedo /home/gfp$ chromium
> Fontconfig error: No writable cache directories
> Fontconfig error: No writable cache directories
> Fontconfig error: No writable cache directories
> Fontconfig error: No writable cache directories
> Fontconfig error: No writable cache directories
> [7535:7535:0422/182050.365759:ERROR:ozone_platform_x11.cc(238)] Missing 
> X server or $DISPLAY
> [7535:7535:0422/182050.366270:ERROR:env.cc(255)] The platform failed to 
> initialize.  Exiting.
> gfp@Tuxedo /home/gfp$
> 

This looks good: You started a login shell with an empty environment, 
(it means when it started, no guix-profile was activated), and the 
commands icecat and chromium were found.

 > I tried to open icecat and chromium in that shell but it doesn’t work.

The reason they printed errors is because the couldn't initialize the 
connection to the window manager, which is necessary for graphical 
applications. The couldn't connect because the environment variable 
DISPLAY was not set (since env - removed it for the shell and it's child 
processes).

So, if icecat and chromium are not installed system wide but only in one 
of your custom profiles, it means they must have been actived by the 
login shell you started. So your .bash_profile seems to work.

Martin Castillo

Re: Help-Guix Digest, Vol 89, Issue 35 (Martin Castillo)

[Gottfried]

[-- Attachment #1.1.1: Type: text/plain, Size: 4715 bytes --]

Hi,

thanks very much for your help.

> But I really mean .xprofile. If it does not exist, create the file and 
>> write
>> 
>> # all Profile beim Start des Displays Managers öffnen
>> source ~/.bash_profile
>> 
>> into it.
>> Also, remove that line from the zprofile.

I did it, and when I use:
Alt + F2 and enter "icecat" it opens

or in the terminal I enter: "icecat" it opens.

But in the application menu there are no icon for "icecat"

So basically I get the packages through Alt + F2 and the terminal
but only the graphical icons in my application meny or the icons, 
shortcuts on the desktop are not there.

So we have a certain success to open the packages from different 
profiles through the two mentioned possibilities.

Of course it would also be fine to have the icons in the GUI, so that I 
know all the packages, which I have in all my profiles installed.

If I forget the name of a package, I have to look in the different 
manifests in the different profiles in order to know the name of the 
package, I installed, and then I can enter that in the terminal or 
through Alt + F2, which is not very handy.

Kind regards

Gottfried


Am 23.04.23 um 14:23 schrieb Martin Castillo:
> Hi,
> 
> Am 22.04.23 um 18:25 schrieb Gottfried:
>> Hi,
>>
>> thanks for help.
>>
>> 1.
>>> To test 1) add
>>>> echo reading xprofile on $(date) >>~/login.log
>>>> to your .xprofile and logout and back in.
>>
>> I have a file .zprofile in my home directory
>> but not a file: .xprofile
>>
> 
> I thought it was a typo in your other mail. zprofile is the startup file 
> for the zsh shell. It's corresponds to the .bash_profile for bash.
> 
> But I really mean .xprofile. If it does not exist, create the file and 
> write
> 
> # all Profile beim Start des Displays Managers öffnen
> source ~/.bash_profile
> 
> into it.
> Also, remove that line from the zprofile.
> 
>> I tried with both to add it to my .zprofile file
>> did not help.
>>
>> ---------------------------------------------------------
>>
>> 2.
>>> 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.
>>
>> I did not find a file: ~/login.log
>>
>> I have  files:
>> .e-log.log
>> .e-log.log.old
>>
>> or they are in a different directory?
>>
> 
> Try again after doing what I wrote above.
> 
>> ------------------------------------------------------------------
>> in /etc/profile there is > I don’t know if that helps, so I copied it
> No, it does not. Unless you changed it in your system config, it's the 
> same every other guix user has on their system.
> 
> 
>> -------------------------------------------------------------------
>>> 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.
>>
>>
>> gfp@Tuxedo ~$ env - $(which bash) -l
>> gfp@Tuxedo /home/gfp$ icecat
>> Error: no DISPLAY environment variable specified
>> gfp@Tuxedo /home/gfp$ chromium
>> Fontconfig error: No writable cache directories
>> Fontconfig error: No writable cache directories
>> Fontconfig error: No writable cache directories
>> Fontconfig error: No writable cache directories
>> Fontconfig error: No writable cache directories
>> [7535:7535:0422/182050.365759:ERROR:ozone_platform_x11.cc(238)] 
>> Missing X server or $DISPLAY
>> [7535:7535:0422/182050.366270:ERROR:env.cc(255)] The platform failed 
>> to initialize.  Exiting.
>> gfp@Tuxedo /home/gfp$
>>
> 
> This looks good: You started a login shell with an empty environment, 
> (it means when it started, no guix-profile was activated), and the 
> commands icecat and chromium were found.
> 
>  > I tried to open icecat and chromium in that shell but it doesn’t work.
> 
> The reason they printed errors is because the couldn't initialize the 
> connection to the window manager, which is necessary for graphical 
> applications. The couldn't connect because the environment variable 
> DISPLAY was not set (since env - removed it for the shell and it's child 
> processes).
> 
> So, if icecat and chromium are not installed system wide but only in one 
> of your custom profiles, it means they must have been actived by the 
> login shell you started. So your .bash_profile seems to work.
> 
> Martin Castillo

-- 



[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: Help-Guix Digest, Vol 89, Issue 35 (Martin Castillo)

[Martin Castillo]

Am 23.04.23 um 15:12 schrieb Gottfried:
> Hi,
> 
> thanks very much for your help.
> 
> I did it, and when I use:
> Alt + F2 and enter "icecat" it opens
> 
> or in the terminal I enter: "icecat" it opens.
> 
Good.


> But in the application menu there are no icon for "icecat"
> 
> So basically I get the packages through Alt + F2 and the terminal
> but only the graphical icons in my application meny or the icons, 
> shortcuts on the desktop are not there.
> 

> Of course it would also be fine to have the icons in the GUI, so that I 
> know all the packages, which I have in all my profiles installed.
> 

That's a problem with the application menu I think. I _think_ it's 
because guix has a different filesystem layout. So someone needs to 
write a patch for that software to search for the icons in the right 
directory.