Re: [gentoo-user] elogind conversion, loginctl user-status fails.

[Steven Lembark]

On Tue, 27 Oct 2020 15:31:22 +
Michael  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

Re: [gentoo-user] elogind conversion, loginctl user-status fails.

[Michael]

On Tuesday, 27 October 2020 14:23:11 GMT Steven Lembark wrote:
> One more elogind update question:
> 
> $ loginctl user-status;
> Could not get properties: is a directory
> 
> Q: Anyone have any idea of what item might be a directory?

loginctl should look into the directory '/run/systemd/sessions/' which 
contains pipes and text files.  The text files contain info on seats, 
sessions, users;  e.g.

# 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
prw--- 1 root root   0 Oct 27 12:11 2.ref
-rw-r--r-- 1 root root 287 Oct 27 12:31 5
prw--- 1 root root   0 Oct 27 12:28 5.ref


> strace doesn't show me anything obvious (which doesn't always
> mean anything).
> 
> 
> 
> Q: Is there any documentation anyone knows about that describes
>this error?
> 
> Thanks

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'?

signature.asc
Description: This is a digitally signed message part.