Alexis wrote:
> Dale <[email protected]> writes:
>
>>> Can someone tell me where/what is supposed to set this and what the
>>> setting is supposed to be?
>
> That's one of the XDG Base Directories:
>
>  https://wiki.gentoo.org/wiki/XDG/Base_Directories
>
> On systemd systems, it will be set by logind. On non-systemd systems,
> elogind can be used to set it.
>
> pam_xdg can also be used to set it, but the ebuild i've created isn't
> yet available in the main repo:
>
>  https://bugs.gentoo.org/908431
>
> Outside of all that, refer to the "Environment variables" sectino of
> this page on the wiki:
>
>  https://wiki.gentoo.org/wiki/Configuring_a_system_without_elogind
>
>
> Alexis.
>
>


Well, those didn't help much directly except to give me some more info
on other things I need to have working correctly.  The wiki page that
helped me, this one. 


https://wiki.gentoo.org/wiki/Elogind


I read down to the part about Pam under Troubleshooting, close to the
bottom.  I was missing a file with a single line.  The other file and
line was there.  This is what was missing, file name and contents. 


root@Gentoo-1 / # cat /etc/pam.d/elogind-user
session optional pam_elogind.so
root@Gentoo-1 / #


I can't logout right now but that is next, when I can stop some things
long enough to do so.  This is the current output of XDG variables. 
Note the missing RUNTIME one.  The file creations hasn't taken effect yet. 


root@Gentoo-1 / # env | grep "XDG"
XDG_CONFIG_DIRS=/home/dale/.config/kdedefaults:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_MENU_PREFIX=plasma-
XDG_SEAT=seat0
XDG_SESSION_TYPE=x11
XDG_CURRENT_DESKTOP=KDE
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_VTNR=7
XDG_SESSION_ID=37
XDG_DATA_DIRS=/usr/local/share:/usr/share
root@Gentoo-1 / #



Oh, I also checked USE flags mentioned in your links, I had those
correctly set.  I had elogind enabled and systemd disabled.  According
to your links, I had that right at least.  No clue how that file and
that one line was missed.  Maybe I caught a ebuild at a bad moment. 

Just to mention, I had to go back to previous version of plasma packages
to fix other things I was having trouble with.  I'm sure the devs are
working hard on it but for some reason, my rig did not like that update
at all.  It had issues.  Maybe the next one will be better. 

Thanks for the links.  It lead me to a possible solution.  I hope
anyway.  I'll post back if it works. 

Dale

:-)  :-) 

Reply via email to