Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 28 |
Nodes: | 6 (0 / 6) |
Uptime: | 51:34:34 |
Calls: | 422 |
Files: | 1,025 |
Messages: | 90,554 |
Hi to Everyone !
vlc 3.0.21 (Vetinari) – Debian 11
⇒ vlc no longer reckognises nor plays mp4 files ; it now only plays their audio part :
« Codec non pris en charge:VLC ne peut pas décoder le format « h264 » (H264
- MPEG-4 AVC (part 10)) »
needless to say that it did work before !
If calling a .ts file with VLC…, I get no error message… but it only plays
the audio part, same as with mp4.
curl -s "https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main
v3/install.sh <https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main>" | bash
On Thu, Apr 17, 2025 at 04:32:26PM +0200, Bernard wrote:
Hi to Everyone !
vlc 3.0.21 (Vetinari) – Debian 11
⇒ vlc no longer reckognises nor plays mp4 files ; it now only plays their >> audio part :
« Codec non pris en charge:VLC ne peut pas décoder le format « h264 » (H264
- MPEG-4 AVC (part 10)) »
needless to say that it did work before !
If calling a .ts file with VLC…, I get no error message… but it only plays
the audio part, same as with mp4.
You /might/ be successful de-installing VLC and re-installing it,
in case this "ISPY" has broken something in your codec installation.
But this is a shot in the dark.
What in earth is ISPY, anyway? Sounds kind of dangerous.
[...]
curl -s
"https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main >>
v3/install.sh
<https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main>" >> | bash
*GAH* :-@
That means that you trust blindly those people. You know this can do
anything to your computer, right?
Cheers
<tomas@tuxteam.de> wrote:As previously said, I already did de-install and purge vlc, then
On Thu, Apr 17, 2025 at 04:32:26PM +0200, Bernard wrote:may also need to purge it.
Hi to Everyone !You /might/ be successful de-installing VLC and re-installing it,
vlc 3.0.21 (Vetinari) – Debian 11
⇒ vlc no longer reckognises nor plays mp4 files ; it now only plays their
audio part :
« Codec non pris en charge:VLC ne peut pas décoder le format « h264 » (H264
- MPEG-4 AVC (part 10)) »
needless to say that it did work before !
If calling a .ts file with VLC…, I get no error message… but it only plays
the audio part, same as with mp4.
in case this "ISPY" has broken something in your codec installation.
But this is a shot in the dark.
What in earth is ISPY, anyway? Sounds kind of dangerous.
same! :)
[...]
curl -s*GAH* :-@
"https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main >>>
v3/install.sh
<https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main>"
| bash
That means that you trust blindly those people. You know this can do
anything to your computer, right?
Cheers
songbird
On 18/04/2025 15:37, songbird wrote:
<tomas@tuxteam.de> wrote:As previously said, I already did de-install and purge vlc, then re-install... in the end, the problem remained : same as before. I
On Thu, Apr 17, 2025 at 04:32:26PM +0200, Bernard wrote:may also need to purge it.
Hi to Everyone !You /might/ be successful de-installing VLC and re-installing it,
vlc 3.0.21 (Vetinari) – Debian 11
⇒ vlc no longer reckognises nor plays mp4 files ; it now only
plays their audio part :
« Codec non pris en charge:VLC ne peut pas décoder le format
« h264 » (H264
- MPEG-4 AVC (part 10)) »
needless to say that it did work before !
If calling a .ts file with VLC…, I get no error message… but it
only plays the audio part, same as with mp4.
in case this "ISPY" has broken something in your codec
installation.
also de-install and purge the ispy software... but I am not sure that
I did remove everything, since I don't know the names of packages ; I
just ran : sudo apt-get purge ispy*... It did seem to do some purge.
But this is a shot in the dark.
What in earth is ISPY, anyway? Sounds kind of dangerous.
The ispy software is something well known, which is available for
Windows, Mac and Linux. It drives several well known "spy cameras",
that is, cameras that spy anything unusual in your garden when there
is no-one at home. If you google search "ispy", you get several pages
of answers.
Thanks for your replies. I will keep searching...
same! :)
[...]
curl -s*GAH* :-@
"https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main
v3/install.sh
<https://raw.githubusercontent.com/ispysoftware/agent-install-scripts/main>"
| bash
That means that you trust blindly those people. You know this can
do anything to your computer, right?
Cheers
songbird
The ispy software is something well known, which is available forIncluding some pretty awful reviews: https://www.reviews.io/company-reviews/store/ispy.com
Windows, Mac and Linux. It drives several well known "spy cameras",
that is, cameras that spy anything unusual in your garden when there
is no-one at home. If you google search "ispy", you get several pages
of answers.
vlc 3.0.21 (Vetinari) – Debian 11
⇒ vlc no longer reckognises nor plays mp4 files ; it now only plays
their audio part :
« Codec non pris en charge:VLC ne peut pas décoder le format « h264 » (H264 - MPEG-4 AVC (part 10)) »
needless to say that it did work before !
If calling a .ts file with VLC…, I get no error message… but it only plays the audio part, same as with mp4.
True enough, during the process of installing ISPY, there was a
warning… but, everyone knows what it is, in the rush I forgot to take precise note of said warning. It said something like this, as far as I
can remember :
« Your system (or such or such component…) is too slow. Would you
accept to increase this or that… ? It won’t pose problem to your
system, but it might affect some components... (Y/N) »
I then replied « Y », in the reasoning that I could, in case of
problem, reverse the situation in removing and purging the ISPY
package.
As previously said, VLC now disfunctions. Maybe something else will
also dysfunction, but I haven’t yet come across such finding.
Once installed, ISPY seemed to work, but I soon found that it wasn’t
what I had expected, so I decided to discard it, and to return the
ISPY camera to where I had bought it.
I had installed this package using the command line below :
Once I found that VLC no longer worked OK, I first tried to reinstall
VLC. The version available for install happened to be the same one as
that I already had, that is, 3.0.21. So, I did remove and purge it,
then re-installed 3.0.21
Problem is, when I tested this newly installed VLC, it did behave as previously, that is, it refused to play the video part of mp4 files
and displayed the previously mentioned error message.
Next, I tried to play those mp4 and ts using ‘Vidéos’ instead of vlc :
"- Impossible to read the file – Decoder H 264 is required to read
this file, but it is not installed… Unfortunately, this H 264 decoder
is not found on your system…"
Must have been there before, though !!
On Sat, 19 Apr 2025 at 04:21, David Wright <deblis@lionunicorn.co.uk> wrote:
You could run a command like:If that command produces any output, then adding a custom format
$ aptitude search "?narrow(?installed,?not(?archive(stable)))"
to see whether all the packages on your system originate in bookworm.
argument to it will help to show why. Suggestion:
aptitude search "?narrow(?installed,?not(?archive(stable)))" -F '%c %M
%p %v %a %O %t %V - %d'
(the suggestion is one single line with no line breaks, ignore
any wrapping that might be added by my mail software)
On Sat, 19 Apr 2025 at 04:21, David Wright <deblis@lionunicorn.co.uk> wrote:
You could run a command like:If that command produces any output, then adding a custom format
$ aptitude search "?narrow(?installed,?not(?archive(stable)))"
to see whether all the packages on your system originate in bookworm.
argument to it will help to show why. Suggestion:
aptitude search "?narrow(?installed,?not(?archive(stable)))" -F '%c %M
%p %v %a %O %t %V - %d'
(the suggestion is one single line with no line breaks, ignore
any wrapping that might be added by my mail software)
Hi to Everyone !..........
vlc 3.0.21 (Vetinari) – Debian 11
⇒ vlc no longer reckognises nor plays mp4 files ; it now only plays
their audio part :
« Codec non pris en charge:VLC ne peut pas décoder le format « h264 » (H264 - MPEG-4 AVC (part 10)) »
needless to say that it did work before !
I did reply to your message, sending the output of suggested aptitude
search below... but my reply does not appear to the list messages,
maybe because there were too many lines in it. In any case, I didn't
find anything meaningfull to me... which doesn't mean that there was nothing...
I just posted a new message saying that I saw messages from a number
of people having lost the use of H264 right after an update of their
Debian 11... and that I found that my late install of ISPY/AgentDVR
had carried an update... Still, I haven't solved my problem.
I think you should post your /etc/apt/sources.list here before
taking further actions.
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
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
# deb cdrom:[Debian GNU/Linux 11.6.0 _Bullseye_ - Official amd64
NETINST 20221217-10:42]/ bullseye main
#deb cdrom:[Debian GNU/Linux 11.6.0 _Bullseye_ - Official amd64
NETINST 20221217-10:42]/ bullseye main
deb http://deb.debian.org/debian/ bullseye main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security
main
# bullseye-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.debian.org/debian/ bullseye-updates main
deb-src http://deb.debian.org/debian/ bullseye-updates main
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
On Tue 22 Apr 2025 at 14:48:01 (+0200), Bernard wrote:
On 21/04/2025 22:02, David Wright wrote:Well, it looks like a normal bullseye list, and the log that
I think you should post your /etc/apt/sources.list here beforeHere it is, dated 22apr2023 : Date shows that I musn't have updated
taking further actions.
it, even though I thought I had
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.
Bernard 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.
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.
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.
So, what would you advise to do from there ?
On Thu 01 May 2025 at 20:04:56 (+0200), Bernard wrote:
On 01/05/2025 06:10, David Wright wrote:I don't know, because the install process does more than just unpack
I could suggest that you reinstall the library file packages if/*I could suggest that you re-install…*/
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.
(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.
the archive—but exactly what?
…/*about linux links libraries… you might check the modificationSo, at first sight, that appears to have been polluted by whatever
timestamps of those /etc files to see whether anything happened on 10
april …*/
ld.so.cache April28 21:07
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 2022Downgrading is rarely straightforward.
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.
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.