Hi Ian, On Mi 19 Sep 2018 16:59:30 CEST, Ian Jackson wrote:
I think this is not happening because of the dependency on `systemd'. That is indeed not the pid 1 part. The root cause of this is dbus-user-session => libpam-systemd => systemd-shim | systemd-sysv but systemd-shim is RC-buggy. The bugs in systemd-shim that are keeping it out of testing are detailed here https://tracker.debian.org/pkg/systemd-shim and are currently (I think): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901404 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901405 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893819 I would be happy to sponsor an upload to fix this. Long term, systemd-shim is undesirable. AIUI the main functionality needed by the desktop environments that is provided by systemd-logind is permissions handling: specifically, arranging that the user currently logged in on the console can do certaain things. An alternative approach that would probably satisfy sysvinit users would be to simply add, as a matter of configuration, appropriate users to a Unix group with equivalent power. Ian.
many thanks for all this background info. I might have a potential contract to get this solved in the loop, so, I may probably return to it soon (or not so soon). Let's see...
Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgphOs0oSByKw.pgp
Description: Digitale PGP-Signatur
