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

Cristian Ionescu-Idbohrn cristian.ionescu-idbohrn at axis.com
Sun Sep 22 08:52:37 BST 2019

On Sat, 21 Sep 2019, Mark Hindley wrote:
> On Sat, Sep 21, 2019 at 06:51:16PM +0200, Cristian Ionescu-Idbohrn wrote:
> > > Would you, please, start a new bug for this unless you really think 
> > > it is the same issue (apt being broken by continuing to uninstall 
> > > libsystemd0 after systemd prerm fails) and I will be happy to help.
> > 
> > I really don't know what to think, but I do really feel this is not 
> > related to the systemd installed version.  Any current systemd version 
> > should be removed without affecting the state.  Am I wrong?
> I have to admit I am not clear exactly what you see is the problem. 
> Is it that removing systemd is taking lots of other packages with 
> it?
> Looking at the list of removals I think it is libpolkit-qt-1 that is 
> taking everything else out becuase it has not been patched to 
> support the new logind virtual packages. See #925344.
> But I still don't think it is the same as Simon's original bug here.


I think you're right.  I'll wait until the polkit-qt packages are 
patched, and if that does not solve my problem I'll submit a bug.



More information about the Debian-init-diversity mailing list