[Solved] Twitter videos suddenly not playing
-
This had been working fine. I'm not sure when it happened, but now videos from Twitter, whether on-site or embedded, are not working. I tried that embedded page in a backup browser, Min, and it did work there.
I recently did a fresh Linux install, so maybe that's at fault, but I'm not sure what to do about it.
-
It seems a issue with proprietary Audio and Video on Linux
Check this article and let us know if it's working fine. -
Thanks much. MX17 Linux has a utility to install that codec, but evidently it doesn't place it in vivaldi's directory. And the MX (Debian) repository doesn't have the chromium-codec, so the command didn't work either.
Instead, I found the codec on github, and copied it to the /opt/vivaldi directory. And it seems to be working fine.
Thanks again.
-
Glad to know it's working fine.I will tag the post as Resolved.
-
This is the github repo that works: https://github.com/liberodark/Chromium-Codecs
-
@paul1149 said in [Solved] Twitter videos suddenly not playing:
Thanks much. MX17 Linux has a utility to install that codec, but evidently it doesn't place it in vivaldi's directory. And the MX (Debian) repository doesn't have the chromium-codec, so the command didn't work either.
Instead, I found the codec on github, and copied it to the /opt/vivaldi directory. And it seems to be working fine.
Thanks again.
I don't think that's the proper to take care of the issue. I think if you do it the way you did, you could run into problems again in the future.
Instead, see Ruari's script, which I think covers many different flavours of Linux:
https://gist.github.com/ruario/bec42d156d30affef655I'm on Mint 18.3, and this is what I have for taking care of video content, including flash:
sudo add-apt-repository "deb http://archive.canonical.com/ubuntu `lsb_release -cs` partner" sudo apt-get update sudo apt-get install chromium-codecs-ffmpeg-extra sudo apt install adobe-flashplugin
-
@ugly said in [Solved] Twitter videos suddenly not playing:
I don't think that's the proper to take care of the issue. I think if you do it the way you did, you could run into problems again in the future.
I'm not clear on why that would be. I placed the codec in a non-version-specific system folder, where it would help all users rather than just my own account. That ~/.local/... hierarchy doesn't even exist on my machine. The procedure I followed is the one recommended by the Slimjet devs.
I'll hold onto that repository spec, though, in case there's ever a need. Thanks.
-