Re: Bash isn't reading ~/.profile file when login from GNOME
On Wed, Aug 21, 2019 at 10:43:18AM -0400, Greg Wooledge wrote:
> wooledg:~$ ls -l /etc/environment.d
> total 8
> -rw-r--r-- 1 root root 20 Aug 21 10:18 11-foo.conf
> -rw-r--r-- 1 root root 19 Feb 9 2019 90qt-a11y.conf
> wooledg:~$ cat /etc/environment.d/90qt-a11y.conf
> QT_ACCESSIBILITY=1
> wooledg:~$ cat /etc/environment.d/11-foo.conf
> FOO=$HOME/thissucks
>
> Seriously, what does it TAKE? Why does QT's work but not mine?
... because they're not actually doing it that way.
wooledg:~$ grep -rF QT_ACCESS /etc 2>/dev/null
/etc/X11/Xsession.d/90qt-a11y:QT_ACCESSIBILITY=1
/etc/X11/Xsession.d/90qt-a11y:export QT_ACCESSIBILITY
/etc/X11/Xsession.d/90qt-a11y: dbus-update-activation-environment --verbose --systemd QT_ACCESSIBILITY
/etc/environment.d/90qt-a11y.conf:QT_ACCESSIBILITY=1
They spammed this variable in multiple places, hoping that at least
one of them would work. Which... it did. Just not the one I thought.
Also, I did some more Google searching and came across
<https://github.com/systemd/systemd/issues/7641>. Which seems to be
saying "sorry, this isn't going to work, we didn't intend for these
environment variables to be used in user login environments".
So just what the hell are they FOR, then?
Another morning wasted on bullshit that does not work and is not ever
going to work and is not even going to be DOCUMENTED as not working.
I guess they enjoy watching us bash our heads against their brick walls
over and over.
Reply to: