The LM module is claiming to parse /run/systemd/sessions/$XDG_SESSION_ID but it is actually looking at /var/run/systemd/sessions/$XDG_SESSION_ID. This is causing problems for systems where /var/run is not linked to /run such as Guix System with elogind.
The /run/systemd/sessions/$XDG_SESSION_ID file exists and has the expected contents. /var/run/systemd does not exist.
I don't know if changing to /run uncoditainally causes some problems on other systems. I have checked a recent debian and fedora system and there /var/run -> /run.
Also the defined macro FF_SYSTEMD_SESSIONS_PATH does not seem to get used at all.
General description of bug:
Hi,
The LM module is claiming to parse
/run/systemd/sessions/$XDG_SESSION_ID
but it is actually looking at/var/run/systemd/sessions/$XDG_SESSION_ID
. This is causing problems for systems where/var/run
is not linked to/run
such as Guix System with elogind.The
/run/systemd/sessions/$XDG_SESSION_ID
file exists and has the expected contents./var/run/systemd
does not exist.I don't know if changing to
/run
uncoditainally causes some problems on other systems. I have checked a recent debian and fedora system and there/var/run -> /run
.Also the defined macro
FF_SYSTEMD_SESSIONS_PATH
does not seem to get used at all.