Abrowser not playing soundfiles - problem with libavcodec?
Hi everybody,
for quite a while already i sometimes have been getting a notification in Abrowser right below the bookmarks, saying:
libavcodec may be vulnerable or is not supported and should be updated to play video
Now, i notice that i can't play (i.e. stream) audiofiles in the browser, on different internet sites.
Looking into Synaptic, libavcodec54 is installed and updated. Could this issue have to do with libavcodec at all?
I can play the audiofiles in Midori browser.
This is Trisquel mini.
Any suggestions?
I am a translator!
https://trisquel.info/en/forum/incompatibilidad-en-abrowser-con-libavcodec#comment-107041
This works, if you trust adding the ppa, which is your decision, and something I never recommend, but I like to let people choose for themselves, because I like freedom...
sudo add-apt-repository ppa:heyarje/libav-11
sudo apt-get update
sudo apt-get install libav-tools libavcodec-extra-56
sudo apt-get upgrade
sudo apt-get dist-upgrade
It works.
Thanks SuperTramp83
I am a translator!
Nice! You welcome
I guess Abrowser is one of the most important/ most used programs in Trisquel, and it is one of this distro's few distinctive programs. For over a month now this basic program has not been able to perform as basic a task as streaming audio files. Seemingly because Trisquel can not keep up with the development of Firefox.
Am i getting this right? Why is there no official patch for this? And has this issue been a matter of debate or criticism anywhere, or have the Trisquel critics already left this forum?
In abrowser, go into about:config and set 'media.libavcodec.allow-obsolete' to 'True'. Restart abrowser and it will no longer issue that warning. I suspect that upstream firefox disables older libavcodec implementations for a very good security reason, but I'm too busy to research that at the moment. Use this solution at your own risk.
The better solution would be to have an updated libavcodec package offered in the Trisquel repos.
Today's libavcodec updates from the Trisquel repositories have solved the problem.
On 08/01/17 20:26, wrote:
> Today's libavcodec updates from the Trisquel repositories have solved
> the problem.
Great news.
--
Ignacio Agulló · name at domain
I just saw these come through. Thanks to the dev(s) and maintainer(s) of Trisquel.