On 02/02/2023 08:20, Mark Hindley wrote:
> No, you can leave elogind installed. If seatd itself is present libseat1
> tries/uses that first. Or you can override the backend to use with the
> LIBSEAT_BACKEND environment variable.

Digging up this old thread again because it occurs to me that "libseat
support" may well have implications for whatever display manager is in
use. As the maintainer of SLiM, this would obviously be of interest to
me. Is there some documentation you can point me to?

Thanks,

Rob

--
Maintainer of the <href="https://sourceforge.net/projects/slim-fork/">SLiM Login Manager fork</a>