Alexis wrote: > Dale <[email protected]> writes: > >> Well, those didn't help much directly except to give me some more info >> on other things I need to have working correctly. > > My apologies, i should have been clearer. > > For others possibly reading this thread in the future, i was trying to > say that, if XDG_RUNTIME_DIR isn't getting set: > > * On a systemd-based system, investigate why logind doesn't seem to > be setting it. (E.g. is systemd-logind running?) > > * On a non-systemd-based system which uses elogind, investigate why > elogind doesn't seem to be setting it. (E.g. is elogind-daemon running?) > > * On a non-systemd-based system which doesn't use elogind, two > options are: > > * Use pam_xdg, although it's not currently in the main repo. > > * Use the shell snippet described in the "Environment variables" > section of the "Configuring a system without elogind" page. > > > Alexis. > >
I'm on a openrc system with elogind running. When I was on the boot runlevel and on a Console, CTRL ALT F1, it shows the RUNTIME as being set. I think it was to /tmp or something. I just saw it set and thought the file I added was fixing it. I checked it after restarting elogind with the new file and option in place. When I went back to default runlevel and logged into KDE, it was no longer set when I checked in Konsole. It seems something unsets it when I login or during the startup of KDE. You have any idea what could cause elogind not to set this or maybe more likely, something unsetting it after elogind is running? I'm thinking the last one because it was set until I got logged back in again. If you need info, just let me know. I tend to run Konsole as root. Let me know if I need to run a command as a user, in case the output is different. Thanks for any help you can provide. From everything I've found, it should work. It's just not working. Dale :-) :-)
