On Tue, 27 Oct 2020 15:31:22 +0000
Michael <confabul...@kintzios.com> wrote:
> loginctl should look into the directory '/run/systemd/sessions/'
> # ls -la /run/systemd/sessions/
> total 8
> drwxr-xr-x 2 root root 120 Oct 27 12:31 .
> drwxr-xr-x 7 root root 140 Oct 27 12:11 ..
> -rw-r--r-- 1 root root 276 Oct 27 12:31 2
Hmmm...
# ls -al /run/systemd/sessions/
total 0
drwxr-xr-x 2 root root 40 Nov 19 11:57 .
drwxr-xr-x 6 root root 120 Nov 19 11:57 ..
i.e., nada.
$ ps aux | grep login;
root 22153 0.0 0.0 3680 2260 ? S 11:57 0:00 elogind-daemon
i.e., elogin is out there, just not creating the session data?
I don't use a graphical login, just command line. Don't know if
that makes a difference.
I've noticed that booting a runtime system w/ systemd & graphical
login has no problems logging me in; running xinit from the command
line is where I run into tty permission issues. That may be a symptom
of something not right here also.
> I don't know of any documentation to point you towards. It could be
> a permissions problem, in the first instance I would start with
> /run/systemd/ sessions/ which should be owned by root.
>
> PS. If you converted your system to run with elogind recently, did
> you set up the requisite USE flag and re-emerged @world with
> '--newuse'?
$ grep login /etc/portage/make.conf;
USE="... elogind -consolekit -systemd";
After that I simply did an "emerge @world" (gcc had been updated,
etc, seemed like a nice time to sync it all up).
At this point I no longer can due to python issues, but the world
we re-emerged at that time.
--
Steven Lembark
Workhorse Computing
lemb...@wrkhors.com
+1 888 359 3508
