Am 04.04.2018 um 21:06 schrieb Michael Biebl: > Am 04.04.2018 um 20:20 schrieb Axel Beckert: >> Hi, >> >> Simon McVittie wrote: >>>> This looks like there is a libglib-2.0.so.0 in /lib/arm-linux-gnueabihf/ >>>> that shouldn't be there, and this takes precedence over the more recent >>>> one from the Debian package that gets installed to /usr/lib. >>> >>> My thoughts exactly. What's that doing there? I would have expected that >>> removing the old libglib2.0-0 package would delete that. >>> >>> Please try: >>> >>> ls -il /lib/arm-linux-gnueabihf/libglib-2.0.so* >> >> 6080 lrwxrwxrwx 1 root root 23 Apr 4 09:03 >> /lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1 >> 1563 -rw-r--r-- 1 root root 814280 Nov 13 2014 >> /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 > > Where is this file /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 > coming from? > Does dpkg list it as owned by any package?
Sorry, somehow completely missed the following paragraph where you answered that already. Do you have an idea, where this file might have come from? So it looks like a local misconfiguration which went unnoticed so far as /lib/arm-linux-gnueabihf/libglib-2.0.so.0.5* took precedence over /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 I guess there is nothing really the libglib2.0-0 package can do about this. Do you agree? As soon as you clean up the stray /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 and run ldconfig, the problem should go away?
Description: OpenPGP digital signature