From: Gottfried <gottfried@posteo.de>
To: Martin Castillo <castilma@uni-bremen.de>, help-guix@gnu.org
Subject: Re: Help-Guix Digest, Vol 89, Issue 35 (Martin Castillo)
Date: Sun, 23 Apr 2023 13:12:46 +0000 [thread overview]
Message-ID: <53562392-de16-1567-3a49-ffad1ca56fea@posteo.de> (raw)
In-Reply-To: <b2d112aa-ac12-1c36-5732-0f59ffd99fd2@uni-bremen.de>
[-- 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 --]
next prev parent reply other threads:[~2023-04-23 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 16:25 Help-Guix Digest, Vol 89, Issue 35 (Martin Castillo) Gottfried
2023-04-23 12:23 ` Martin Castillo
2023-04-23 13:12 ` Gottfried [this message]
2023-04-23 15:02 ` 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=53562392-de16-1567-3a49-ffad1ca56fea@posteo.de \
--to=gottfried@posteo.de \
--cc=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).