[pkg-cryptsetup-devel] Bug#963721: Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow
Christian Weeks
cpw at weeksfamily.ca
Sat Jun 27 01:39:32 BST 2020
Update. I just discovered steam is still broken. After some more googling,
it seems that the REAL culprit might be libmount1.
Specifically, it seems that libmount1 v2.35.2-5 (bug #951048) has started
building with libcryptsetup-dev, but that is causing weird SSL leakages
everywhere, crashing unrelated software (minecraft launcher, steam, other
stuff using SSL).
I have upgraded libcryptsetup12 and downgraded libmount1 to 2.35.2-4
and it has resolved the problem as well.
This seems like a really messy tangled web of nastiness. Good luck figuring it
out.
I'm going to speculate that the guys at Mandriva found a similar problem:
https://github.com/ValveSoftware/steam-for-linux/issues/6861
Perhaps they might have a solution too?
Thanks
On Fri, 2020-06-26 at 11:40 -0400, Christian Weeks wrote:
> Attached is the output of the various console commands, as well
> as the backtrace from the broken launcher with the new lib.
>
> Note that I am installing both amd64 and i386 versions. I do not
> have cryptsetup even installed on this machine, I think this lib
> is coming in from a dependency in gnome disks.
>
> There is one key difference: in the older version, there is an
> explicit libssl in the linker, but in the new version, there
> is not, even though it is somehow still being loaded.
>
> Perhaps another lib is pulling a differing version somehow, and
> this lib is stamping on it?
>
> Thanks!
>
> On Fri, 2020-06-26 at 17:23 +0200, Guilhem Moulin wrote:
> > Control: tag -1 moreinfo
> >
> > Hi Christian,
> >
> > On Thu, 25 Jun 2020 at 21:58:43 -0400, Christian Weeks wrote:
> > > I installed the newest version of libcryptsetup12.
> >
> > Unfortunately you appeared to file this bug using Buster's
> > libcryptsetup12 so the metada doesn't describe the buggy environment
> > (Version: 2:2.1.0-5+deb10u2). Please show the output of `apt upgrade
> > libcryptsetup12` that yields the buggy environment. (I.e., you don't
> > encounter the bug before the command but do after the upgrade.) The
> > output of
> >
> > ldd /lib/*-linux-gnu/libcryptsetup.so.12.6.0 /sbin/cryptsetup
> >
> > and
> >
> > dpkg-query -l "*cryptsetup*"
> >
> > before *and* after the upgrade might be helpful too.
> >
> > > Suddenly, minecraft would not run!
> > > Backtraces in gdb indicate that something is broken in SSL.
> >
> > Care to share said backtrace also?
> >
> > cheers
More information about the pkg-cryptsetup-devel
mailing list