Solved [Solved] HTML5 codecs, again

Ruarí

Ok, let's remove the entire timeout from the script, like so

sudo sed -i '/^  DOWNLOAD/s/ -T[0-9]\+//' /opt/vivaldi/update-widevine

Then re-run it

sudo /opt/vivaldi/update-widevine

paul1149

@ruario You nailed that one! But I then retried ffmpeg, and same problem there.

$ sudo /opt/vivaldi/update-widevine
Widevine (4.10.1440.18) installed successfully (PLEASE RESTART VIVALDI)

However, support for 'proprietary media' is not installed. Fix this by running:
    /opt/vivaldi/update-ffmpeg

paul@mx19:~
$ /opt/vivaldi/update-ffmpeg
You may need to be root (or rerun this command with sudo)
mkdir: cannot create directory ‘/var/opt/vivaldi/media-codecs-78.0.3904.70’: Permission denied
paul@mx19:~
$ sudo /opt/vivaldi/update-ffmpeg
xz: (stdin): File format not recognized
tar: This does not look like a tar archive
tar: ./usr/lib/chromium-browser/libffmpeg.so: Not found in archive
tar: Exiting with failure status due to previous errors
The extracted libffmpeg.so does not match the expected sha256sum; aborting

Ruarí

Ok, same fix then

sudo sed -i '/^  DOWNLOAD/s/ -T[0-9]\+//' /opt/vivaldi/update-ffmpeg

sudo /opt/vivaldi/update-ffmpeg

EDIT: For anyone else who has this issue, the following should work if for snapshot and stable. It will remove the timeout from both scripts (it assumes bash). Clearly the timeout is too short for many people's networks.

sudo sed -i '/^  DOWNLOAD/s/ \(-T\|--connect-timeout \)[0-9]\+//' /opt/vivaldi*/update-{widevine,ffmpeg}

paul1149

@ruario Dude, you nailed it. Thanks!

Two questions then. How do I remediate my friend's machine with the same problem? I guess I go through these same steps.

Second, is there a way to prevent this problem from happening in new installs?

There's also the issue of why this apparently happens only on MX and not other Linux distros.

Ruarí

@paul1149 said in HTML5 codecs, again:

@ruario Dude, you nailed it. Thanks!

Two questions then. How do I remediate my friend's machine with the same problem? I guess I go through these same steps.

sudo sed -i '/^  DOWNLOAD/s/ \(-T\|--connect-timeout \)[0-9]\+//' /opt/vivaldi*/update-{widevine,ffmpeg}

Second, is there a way to prevent this problem from happening in new installs?

Yes… I need to fix it in the source and ship an updated Vivaldi that includes the fix.

There's also the issue of why this apparently happens only on MX and not other Linux distros.

It is almost certainly nothing to do with MX and more to do with you having a slower connection than I predicted when I added a short 3 second timeout.

EDIT: We have had other reports that were likely this from several distros

Ruarí

@Gwen-Dragon This could also happen if a user had defined a proxy that wget is configured to use (for their user but not for root). Though I am not sure how I would handle that other than print out a more meaningful message when I suspect it happens.

paul1149

@ruario Ok, thanks. Maybe I'll wait for the update and let him do that. I also didn't think that a timeout would spawn the kind of error messages that I got, but obviously it is the case. Thank you for your expertise, and thank you @Gwen-Dragon for your help and patience too.

os24

@lamarca ./thanks it work for me

lamarca

@os24 Glad to know!

pointed.stick

After updating from 4.3 to 5.0 HTML5 media stopped working...

sudo  /opt/vivaldi/update-ffmpeg

returns with

Your glibc version is too old to search for a replacement libffmpeg that supports proprietary media

glibc version is 2.19

DoctorG

@pointed-stick You need to update to a never version of your Linux.
https://forum.vivaldi.net/topic/69365/requirement-of-glibc-for-libffmpeg-so-media-codec/

pointed.stick

Ah. "Won't fix."

That's just great.

DoctorG

@pointed-stick Sorry to say, but if you do not compile your own glibc to be used with current Chromium libffmpeg, this will not be fixed.

pointed.stick

32-bit users were abandoned before Vivaldi 4. Now users with older installations.

Just great.

DoctorG

@pointed-stick 32bit versions do not build anymore in compiling process and the Vivaldi team is not large enough to investigate and fix the Chromium 32bit problems.
And you can be sure i dislike the problem with 32bit Chromium code too, i own a 32bit Atom Netbook which can not use Vivaldi anymore.

The issue with glibc is not nice but Vivaldi needs current libffmpeg from Chromium to get non-free media encodings working. Blame FFmpeg for their paid license policy and money-gaining companies with their non-free codecs.

dmocek

My issue is that I'm behind a proxy and the update does not look at and use the proxy configuration I have set in Vivaldi. So when I run:

sudo /opt/vivaldi/update-ffmpeg

I have to disconnect from VPN, run update-ffmpeg, then reconnect.

evanmoriarty

@paul1149 I was able to run /opt/vivaldi/update-ffmpeg --user, restart Vivaldi, and it fixed my issue of my CPU at 100% when I would play 1080p 60fps videos.

bvamundsen

so # /opt/vivaldi/update-ffmpeg
Your glibc version is too old to search for a replacement libffmpeg that supports proprietary media

gives me the same answer as others on older stable Linux versions. Glad I kept the old 4.x version of vivaldi, which works without issue. Maybe the real issue is that everyone is being pushed by Google/Chrome to bleeding edge. Maybe the issue is that Vivaldi team is too small to help the older stable Linux users. Maybe the old Opera- presto engine is still the way to go. Maybe moving away from anything sponsored by Google is the best path.

Too bad, bye-bye Vivaldi.

paul1149

@evanmoriarty Thanks. No problem here now, but I will hold onto the suggestion.

givfor

I get this as well:

Your glibc version is too old to search for a replacement libffmpeg that supports proprietary media

Disappointing.