Bug#896019: libglib2.0-0: undefined symbol g_date_copy breaking many programs

Simon McVittie smcv at debian.org
Mon Apr 23 17:47:56 BST 2018


On Mon, 23 Apr 2018 at 17:11:11 +0200, Michael Biebl wrote:
> @smcv: Do you think this is a failure of dpkg/apt cleaning up old
> versions? My suspicion is rather, that there is some old copy of libglib
> lying around in /lib/x86_64-linux which was copied there by some 3rd
> party installer, possibly lying around for years there.

That's entirely possible.

> @rektide: the time stamp of
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0.4200.0 would be interesting.

I already asked for "ls -il" output which would tell us the timestamp
(as well as whether various files are hard-links to each other).

> Does that coincide wit the installation of a proprietary/non-Debian
> package or the use of "make install"?

Whether there's a correlation with some other event is also interesting
information, though.

    smcv



More information about the pkg-gnome-maintainers mailing list