Dale wrote:
> 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
>
> :-) :-)
>
OK. My backups finished, sooner than I expected. I logged out, went to
boot runlevel, restarted elogind then checked the variable. I was on a
Console but it showed the RUNTIME one as set, /tmp or something. So, I
thought I had success. I then went back to default runlevel and logged
into KDE. To be sure, I went to a Konsole, within KDE, and checked to
see if it was still set. It is missing from the list. The others are
set but not RUNTIME.
Does this make any sense? It seems that before I login, it is set to
something that looked right at least. As soon as I get logged into KDE,
it is no longer set. Any idea what could be unsetting this when I
login? I've checked everything I can find from the wiki and such. I
have no idea what to check now.
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=39
XDG_DATA_DIRS=/usr/local/share:/usr/share
root@Gentoo-1 / # grep -r XDG_RUNTIME /etc/
/etc/speech-dispatcher/speechd.conf:#
$XDG_RUNTIME_DIR/speech-dispatcher/speechd.sock where $XDG_RUNTIME_DIR
/etc/init.d/user:# If it's rapidly failing, usually due to
XDG_RUNTIME_DIR being unset,
/etc/user/init.d/wireplumber:DBUS_SESSION_BUS_ADDRESS="unix:path=${XDG_RUNTIME_DIR}/bus"
/etc/user/init.d/dbus:dbus_socket="${XDG_RUNTIME_DIR}/bus"
/etc/user/init.d/pipewire:export
DBUS_SESSION_BUS_ADDRESS="unix:path=${XDG_RUNTIME_DIR}/bus"
/etc/user/init.d/xdg-desktop-portal:DBUS_SESSION_BUS_ADDRESS="unix:path=${XDG_RUNTIME_DIR}/bus"
/etc/user/init.d/pipewire-pulse:export
DBUS_SESSION_BUS_ADDRESS="unix:path=${XDG_RUNTIME_DIR}/bus"
/etc/user/init.d/ssh-agent:command_args="-D -a
${XDG_RUNTIME_DIR}/ssh-agent.sock"
/etc/xdg/xfce4/xinitrc: XDG_RUNTIME_DIR \
root@Gentoo-1 / #
I see something for xfce4 but that doesn't look right. It's a backup
GUI. I don't recall ever using it.
Ideas?
Dale
:-) :-)
