On 22/04/2025 21:33, David Wright wrote:
On Tue 22 Apr 2025 at 14:48:01 (+0200), Bernard wrote:
On 21/04/2025 22:02, David Wright wrote:
I think you should post your /etc/apt/sources.list here before
taking further actions.
Here it is, dated 22apr2023 : Date shows that I musn't have updated
it, even though I thought I had
Well, it looks like a normal bullseye list, and the log that
you sent me mentions only bullseye packages, though it indeed
shows that your system had many ungradeable bullseye packages (314).
The log then shows apt-transport-https being installed,
presumably so that it can download AgentDVR. Having extracted
the files from the download, it asks about upgrading
/usr/lib/x86_64-linux-gnu/libva.so.2.1000.0
It then upgrades three packages, installs 84 more, leaving 311
still upgradeable. They all come from bullseye.
I think it then downloads and builds stuff from git. It seems
to say that this all ends up in /usr/local/lib/.
This section is all over my head, particularly when it
talks about using libtool or setting -LLIBDIR etc.
So no, bookworm is not involved. I assume that the packages you
listed before, and I commented on, are some of the 311 still
upgradeable packages, but never having run a machine so behind
in upgrades, I'm not used to seeing output like that. If I find
the time, I'll try to check one or two.
Do you still have the libraries it installed in /usr/local/lib/?
(The /opt/… stuff is less important.) Can you tell whether any
of them are still being used. Being unlearned in this area. my
methodology would be crude: after a period of time (like tomorrow
morning), I'd read the directories with ls -ult, then attempt
and fail to play a video, then repeat the listings to see whether
the access times had changed. (And even this will probably not
work on a laptop.)
If you wanted to post the logs, I think the area of interest is
likely to be after "All build dependencies are installed." but
eliminating the interminable lines starting with "checking ".
That may show others what you need to do to get programs to
link with the correct versions of libraries. As I said, that
stuff is all above my paygrade.
If and when you get the (bullseye) system restored, you might
want to get it up-to-date, even if you don't intend to advance
to bookworm.
Cheers,
David.
Thanks for your help, and sorry for the delay to reply : I’ve been away
for a few days, then tied to urgent garden work…
bd@debian-stretch:/usr/local/lib$ ls -l
total 1000
-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
10 april must be the date I installed that awful ISPY/Agent package
17 april 2023 must be the date of install of my current Bullseye
then :
bd@debian-stretch:/usr/local/lib$ ls -ult
total 1000
lrwxrwxrwx 1 root root 21 29 avril 10:54 libva-drm.so.2 ->
libva-drm.so.2.2200.0
lrwxrwxrwx 1 root root 17 29 avril 10:54 libva.so.2 -> libva.so.2.2200.0
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
-rwxr-xr-x 1 root root 50896 28 avril 01:20 libva-drm.so.2.2200.0
-rwxr-xr-x 1 root root 953408 28 avril 01:20 libva.so.2.2200.0
drwxr-xr-x 2 root root 4096 21 avril 10:38 pkgconfig
drwxr-xr-x 3 root root 4096 21 avril 10:38 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
29 april 10:54 is… a few minutes ago
Then, I made another attempt to run a mp4 video file using most recent
‘vlc’, getting the usual displayed error message :
Codec non pris en charge:
VLC ne peut pas décoder le format « h264 » (H264 - MPEG-4 AVC (part 10))
Then, right after this : I, once more, removed and purged VLC, then
re-installed it. This being done :
bd@debian-stretch:/usr/local/lib$ ls -ult
total 1000
-rwxr-xr-x 1 root root 50896 29 avril 11:17 libva-drm.so.2.2200.0
-rwxr-xr-x 1 root root 953408 29 avril 11:17 libva.so.2.2200.0
lrwxrwxrwx 1 root root 21 29 avril 10:54 libva-drm.so.2 ->
libva-drm.so.2.2200.0
lrwxrwxrwx 1 root root 17 29 avril 10:54 libva.so.2 -> libva.so.2.2200.0
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
drwxr-xr-x 2 root root 4096 21 avril 10:38 pkgconfig
drwxr-xr-x 3 root root 4096 21 avril 10:38 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
29 april 11:17 is when the de-install re-install of ‘vlc’ was carried,
then the test was run attempting to play a mp4 file with VLC. Same error
message as previously.
As I found soon after, the changes shown in ls -ult are solely due to
the re-install of the VLC package… any more call to
vlc myfile.mp4
no longermodify the results of
usr/local/lib/ ls -ult
Thanks in advance for your replies
Bernard
