Am 31.01.20 um 05:40 schrieb Benda Xu: > Hi Michael, > > What is the status of this bug? > > > elogin now provides sd_uid_is_on_seat: > > $ nm -D /lib/elogind/libelogind-shared-241.3.so | grep sd_uid_is_on_seat > > 00000000000b5b90 T sd_uid_is_on_seat > > > Please express your concern.
The libpam-systemd dependency was added in 2.1.3-2. Here's the relevant changelog entry > udisks2 (2.1.3-2) unstable; urgency=medium ... > * debian/control: Add dependecy against libpam-systemd, we need to be sure a > logind session is registered for seat detection and system inhibitors > > -- Laurent Bigonville <[email protected]> Sat, 31 May 2014 22:40:10 +0200 The seat detection is acquired via libsystemd, not the D-Bus interface afaics. The virtual package logind only provides guarantees regarding the D-Bus interface. From /usr/share/doc/debian-policy/virtual-package-names-list.yaml.gz - name: logind description: an org.freedesktop.login1 D-Bus API implementation (versioned) Can you provide more information if the C-API of logind is fully implemented in elogind? Should debian-policy be updated then? That is my concern number one. Second, I don't think the logind virtual package gives any guarantees regarding the systemd inhibit API. How does elogind enforce an inhibition lock? Say udisks currently executed a destructive operation operation. How does it prevent (accidental) shutdowns in this case, which would render your system broken? Regards, Michael
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-utopia-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
