Am Fri, 27 Mar 2020 02:05:56 +0100 schrieb Zelphir Kaltstahl <[email protected]>:
> > Hello Zelphir,
> > I had a similar problem with other window managers, because of not using
> > .profile.
> > (I use tcsh as a shell)
> > I don't know Guix, but it may be the same solution would work for you too.
> > 1.) Edit (or create) ~/.pam_environment (Attached the content of my file)
> > 2.) You need also some packages libpam-runtime libpam0g libpam-modules
> > libpam-modules-bin libpam-systemd
> > (You probably have them already)
> > It should work with the next login.
> >
> > Kornel
>
>
> Hi Kornel!
>
> You were right! I found an even easier solution though:
>
> My ~/.profile definitions are not visible to a program installed via
> Guix, when it starts. So I looked around in my Guix profile folder at
> ~/.guix-profile and found an etc/profile in there. There I add my
> variables, just like in ~/.profile and tada! LyX starts just fine. I
> guess, that LyX only worked the first time correctly, because the Guix
> daemon was already started and did not read the default definitions in
> that ~/.guix-profile/etc/profile without rebooting or relogin. So when I
> started my machine the next day, it suddenly started seeing those wrong
> default variable values in there. Now that I changed them in there,
> after a relogin everything works as expected. No more errors on command
> line output.
>
> Not sure whether that profile file will be overwritten in the future,
> but if that happens I will notice and search for a Guix best practice
> regarding environment variables.
>
> Thank you for your help and hints!
>
> Regards,
> Zelphir
Your ~/.guix-profile are safe.
Thanks for the confirmation.
Kornel
pgpJHyZOh69PN.pgp
Description: Digitale Signatur von OpenPGP
-- lyx-users mailing list [email protected] http://lists.lyx.org/mailman/listinfo/lyx-users
