On Wed 30 Apr 2025 at 16:53:43 (+0200), Bernard wrote: > On 30/04/2025 01:34, David Wright wrote: > > And at that point, I would have looked again at ls -ult > > to see whether anything had changed. > > Well, running vlc at about the same time as reinstalling it > > makes sure that any data you collect is as ambiguous as possible. > > So, I just tested it again : this time : > $ vlc myfile.mp4 > gave the same error msg as previously, but the result of > ls -ult > was different : > > bd@debian-stretch:/usr/local/lib$ ls -ult > total 1000 > -rwxr-xr-x 1 root root 50896 30 avril 16:27 libva-drm.so.2.2200.0 > -rwxr-xr-x 1 root root 953408 30 avril 16:27 libva.so.2.2200.0 > lrwxrwxrwx 1 root root 21 30 avril 16:09 libva-drm.so -> > libva-drm.so.2.2200.0 > lrwxrwxrwx 1 root root 21 30 avril 16:09 libva-drm.so.2 -> > libva-drm.so.2.2200.0 > lrwxrwxrwx 1 root root 17 30 avril 16:09 libva.so -> libva.so.2.2200.0 > lrwxrwxrwx 1 root root 17 30 avril 16:09 libva.so.2 -> libva.so.2.2200.0 > drwxr-xr-x 2 root root 4096 30 avril 15:16 pkgconfig > drwxr-xr-x 3 root root 4096 30 avril 15:16 python3.9 > -rwxr-xr-x 1 root root 979 10 avril 17:59 libva-drm.la > -rwxr-xr-x 1 root root 925 10 avril 17:59 libva.la > > 16:09 was the time when I first ran ls -ult > 16:29 was when I ran > vlc myfile.mp4 > > and got the usual error message. The other lines kept same time access > as before the call of vlc.
The first two file entries show that something, presumably vlc, is still reading the library files. > Next 4 lines acces times remained unchanged > from that of first call to ls -ult ; however, if one exept the two > last lines, they all where tagged april 30th, that is, today a bit > earlier. The four lines don't change because the system remembers the locations of the symlink targets. The two .la files are not read any more, as they were only needed a fortnight ago, at build time. I could suggest that you reinstall the library file packages if that didn't happen when you reinstalled vlc, but it's perfectly possible that the Debian versions of the libraries are in place already: lrwxrwxrwx 1 root root 21 Dec 6 2020 /usr/lib/x86_64-linux-gnu/libva-drm.so.2 -> libva-drm.so.2.1000.0 -rw-r--r-- 1 root root 14504 Dec 6 2020 /usr/lib/x86_64-linux-gnu/libva-drm.so.2.1000.0 lrwxrwxrwx 1 root root 17 Dec 6 2020 /usr/lib/x86_64-linux-gnu/libva.so.2 -> libva.so.2.1000.0 -rw-r--r-- 1 root root 178736 Dec 6 2020 /usr/lib/x86_64-linux-gnu/libva.so.2.1000.0 l I don't know enough about how linux links libraries to say whether reinstalling those libraries would revert everything, or whether something could have polluted files like /etc/ld.so.* and /etc/ld.so.conf.d/*, which could cause /usr/local/lib/ to continue being preferred over the Debian versions. You might check the modification timestamps of those /etc/ files to see whether anything happened on 10 April, but be aware that there's an upgrade available for libc6 and libc-bin at the moment (assuming you haven't already upgraded them in the last 30 hours or so), and that could update timestamps. And anyway, I suspect the timestamp on /etc/ld.so.cache might not be very meaningful, as other things might refresh it. Cheers, David.
