On 02/05/2025 02:34, David Wright wrote:
On Thu 01 May 2025 at 20:04:56 (+0200), Bernard wrote:
On 01/05/2025 06:10, David Wright wrote:
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.
/*I could suggest that you re-install…*/
(four lines dated dec 6 2020… => they are already in place, same date.
So, I suppose that there is no need to re-install, since it is likely
that the library file package did get re-installed when re-installing
vlc.
I don't know, because the install process does more than just unpack
the archive—but exactly what?
It does a lot of things, as I just found when reading
/var/log/agentdvr_setup.log
dated april 10. 'agentdvr' checked my system and found that my libva
version was too old : 2.10 when 2.21+ was required. It proposed to
upgrade to 2.22 and I replied 'Y'. Agentdvr installed it with a long
list of required dependencies listed in the log file. I tried to attach
the file, but then the sending failed.
Do you think that a apt-get update could solve the problem ?
If not, I may try an apt-get dist-upgrade... but I must say that in my
20 yrs of Linux, I always failed dist upgrades, and in the end I every
time had to wipe out everything and reinstall a new version from scratch...
Thanks for your help,
Cheers,
Bernard
…/*about linux links libraries… you might check the modification
timestamps of those /etc files to see whether anything happened on 10
april …*/
ld.so.cache April28 21:07
So, at first sight, that appears to have been polluted by whatever
happened then in /usr/local/lib/:
lrwxrwxrwx 1 root root 21 28 avril 21:06 libva-drm.so ->
libva-drm.so.2.2200.0
lrwxrwxrwx 1 root root 17 28 avril 21:06 libva.so -> libva.so.2.2200.0
ld.so.conf Sept 2022
ld.so.conf.d/ April 10 17:59 ! !
inside this directory :
libva-custom.conf April 10 17:59 – This file contains only one line :
/usr/local/lib,/
/which said /usr/local/lib/ contains 8 filenames, all dated april 10
17:59, and 2 directories, one dated april 10 17:59, the other one
(python 3,9) dated 2023 :/
/-rwxr-xr-x 1 root root 979 10 avril 17:59 libva-drm.la/
/lrwxrwxrwx 1 root root 21 10 avril 17:59 libva-drm.so ->
libva-drm.so.2.2200.0/
/lrwxrwxrwx 1 root root 21 10 avril 17:59 libva-drm.so.2 ->
libva-drm.so.2.2200.0/
/-rwxr-xr-x 1 root root 50896 10 avril 17:59 libva-drm.so.2.2200.0/
/-rwxr-xr-x 1 root root 925 10 avril 17:59 libva.la/
/lrwxrwxrwx 1 root root 17 10 avril 17:59 libva.so -> libva.so.2.2200.0/
/lrwxrwxrwx 1 root root 17 10 avril 17:59 libva.so.2 -> libva.so.2.2200.0/
/-rwxr-xr-x 1 root root 953408 10 avril 17:59 libva.so.2.2200.0/
/drwxr-xr-x 2 root root 4096 10 avril 17:59 pkgconfig/
/drwxr-xr-x 3 root root 4096 17 avril 2023 python3.9/
*cd pkgconfig*
2 files dated 10 april 17:59 : libva-drm.pc and libva.pc
vi libva.drm.pc :
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
display=drm
Name: libva-${display}
Description: Userspace Video Acceleration (VA) ${display} interface
Requires: libva
Version: 1.22.0
Libs: -L${libdir} -lva-${display}
Cflags: -I${includedir}
vi libva.pc :
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
driverdir=${exec_prefix}/lib/dri
libva_version=2.22.0
Name: libva
Description: Userspace Video Acceleration (VA) core interface
Version: 1.22.0
Libs: -L${libdir} -lva
Cflags: -I${includedir}
*********************************************************************************
What triggers most my attention about those files dated 10 april
17:59… is the reference to
Video Acceleration (VA)
which reminds me that, in the installation process of ‘ISPY/AgentDVR’
packages, Video Acceleration was mentioned as a compulsory step, with
a warning that it could eventually affect some other applications ; I
had replied ‘Y’, because I thought it was easily reversible.
Downgrading is rarely straightforward.
So, what would you advise to do from there ?
As I said, this stuff is above my paygrade. I can only say what
I would do, which is probably to move the files out of /usr/local/lib/
(but leave the python directory), then reinstall those libraries.
(If they could be removed without too much collateral damage,
I would remove them, and then install them and whatever else
got removed.) Obviously, test with:
$ apt-get -s … …
before you carry out anything like this.
But I can't take responsibility for someone else's system.
Cheers,
David.
