Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

Adam Borowski kilobyte at angband.pl
Tue Aug 13 21:18:18 BST 2019

On Tue, Aug 13, 2019 at 09:10:12PM +0100, Simon McVittie wrote:
> On Tue, 13 Aug 2019 at 19:58:09 +0100, Mark Hindley wrote:
> > I would also add that it surprises me that apt requires symbols from
> > libsystemd.so.
> libapt-pkg uses sd-bus, systemd's implementation of D-Bus (the same one
> provided by libelogind), to tell systemd-logind (or elogind) not to
> shut down while an apt frontend is still installing packages.
> If apt wants to talk to D-Bus, sd-bus is certainly not a terrible choice:
> newer D-Bus implementations like GDBus and sd-bus have had the opportunity
> to learn from libdbus' mistakes.

Because of consequences of apt failing to run, perhaps this could be ldopened

⣾⠁⢠⠒⠀⣿⡁ Debian is one big family.  Including that weird uncle
⢿⡄⠘⠷⠚⠋⠀ and ultra-religious in-laws.

More information about the Debian-init-diversity mailing list