On Thu, Nov 14, 2019 at 10:52:50PM +0100, Michael Biebl wrote: > Hi, > I suppose > dpkg -S /lib/x86_64-linux-gnu/libseccomp.so.2 > yields nothing. Hello, preciselly right, there was stalled version of libseccomp.so.2 in /lib/x86_64-linux-gnu and removing it helped.
> Which confirms what Sorin also wrote: > You have a library libseccomp.so.2 which is not actually provided by a > debian package. > Libraries in /lib are preferred over libraries in /usr/lib. > So it overrides /usr/lib/x86_64-linux-gnu/libseccomp.so.2 which is > provided by libseccomp2 and thus breaks systemd (or any other user of > libseccomp). > > You need to remove that local copy/installation of > /lib/x86_64-linux-gnu/libseccomp.so.*, then run ldconfig and your > problem should be fixed. > > I'm closing this bug report, as this is not something that can be fixed > in systemd. Actually I have found a bunch of libraries not owned by any package (according to dpkg) in this directory and I am pretty sure I never manually copied them. Clearly this bug is not related to systemd, but I am not sure where should I report it. Thank you. Jan