Solved [Solved] HTML5 codecs, again

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.

givfor

This is really the worst Vivaldi release ever. I am finding Facebook tabs constantly crashing, and/or going up to 5 GB memory usage! It's totally ridiculous, as it makes my system completely unresponsive so I have to kill the process for that tab. That is in addition to videos no longer playing on either Facebook or Bitchute. So I have had to go back to Firefox.

givfor

This is the version number : 5.0.2497.32 (Stable channel) stable (64-bit)
Everything was perfectly fine before installing this update. I find it hard to believe Vivaldi could have released this, it is so bad.

guigirl

@givfor Do you have the same problems when tested in a new virgin profile [& all custom chromium flags reset]?

givfor

@guigirl I have tried setting up a new profile and I have seen the window with that has the same problem - Facebook tab goes up to 4-5 GB after a while and also goes to high CPU (90-120%). I don't know the custom chromium flags you mention so I can't try that.