Bug#954960: steam: new steam update crashes with fatal error: could not load steamui.so

Simon McVittie smcv at debian.org
Thu Mar 26 22:59:06 GMT 2020


On Thu, 26 Mar 2020 at 22:32:25 +0000, Ximin Luo wrote:
> Thanks for the hints. I was able to figure out that somehow I had an
> extra copy of an old glib from May 2018 in /lib, similar to the problem
> described in #896019.

Ugh, it's looking like this is more common than we might have
anticipated...

> sudo rm -f /lib/i386-linux-gnu/libglib-2.0.so.0.3200.4

That's GLib 2.32.4, from Debian 7 'wheezy' (or Ubuntu 12.04 'precise',
or some contemporary version), 2012 or early 2013.

Do you have any idea why it might still be there, even after you
(presumably) upgraded libglib2.0-0:i386 to a much newer version?

Or, do you have any ideas of something significant that might have
happened to this system in May 2018, like disk corruption, encountering
dpkg bugs, applying local workarounds for wrong library dependencies,
that sort of thing?

Do you have any other non-dpkg-owned libraries in /lib/MULTIARCH or in
/usr/lib/MULTIARCH?

I wonder whether it's significant, or just coincidence, that this is the
same GLib version that's in the Steam Runtime?

    smcv



More information about the Pkg-games-devel mailing list