Opera 79 Stable
-
treego last edited by treego
Brave and Vivaldi have no such issues with these updates and libffmpeg.so on Chromebook/Linux. I wish Opera could be more user-friendly. I have to update libffmpeg.so on each update -- but the latest libffmpeg.so at GitHub.com https://github.com/iteufel/nwjs-ffmpeg-prebuilt will not even work with this installation/update of Opera right now.
-
treego last edited by
@gkaczmarek I won't be doing this because it is a libffmpeg.so issue. Opera could do themselves and their users a big favor by updating this file for Linux users. Thank you.
-
pinheadlucas last edited by
@pinheadlucas said:
I can't see Twitch, Youtube and Gmail:
https://freeimage.host/i/RgOeQ2I'm on Parrot OS 4.11 x86_64
-
andrew84 last edited by andrew84
Interesting thing is that there were 2 Stable builds today( 78.0.4093.231 and 79.0.4143.22)
![0_1631646763084_2021-09-14_210926.png](Uploading 0%)
*btw, picture uploading doesn't work currently -
hectormaciasa1979 last edited by
I still don't see the point of having a check for updates button. Every time you go there, it looks automatically for updates and the button is disabled, after it finds nothing (usually), the button is enabled so that you do the same thing again? it's nonsense.
And it's a duplicated function, we already got the about page doing the same and more easily.
-
hectormaciasa1979 last edited by
@ddvddv: Nothing beats AdGuard, it's been the king for years, you people seriously need to mark a distance from AdBlock/AdBlocker/Adblock Plus, etc.
AdGuard and the Built in ad blocker and you're done.
-
chas4 last edited by
@leocg The bug in the updater is 15+ versions old, reported it a long time ago and many others have confirmed it. You get stuck in an infinite loop as the Relaunch Opera button shows before the updater is done and the update fails starting an infinite loop.
Why Open the Web?
Despite the connecting purpose of the Web, it is not entirely open to all of its users.
When used correctly, HTML documents can be displayed across platforms and devices.
However, many devices are excluded access to Web content. -
burnout426 Volunteer last edited by burnout426
@hectormaciasa1979 Note that checking for updates on
opera://about
andopera://update
doesn't work correctly right away when you first start Opera. You have to give the updater process time to load first. Then it'll work fine. So, if you start Opera, wait 30 seconds or so before loading the update page or about page. Then things should work better.Unfortunately, the update and about page code doesn't have a check for this and then a "waiting for update process to load" message. Instead, it just tries to check for updates before the process loads, which always fails and wastes your time.
-
burnout426 Volunteer last edited by
@chas4 I'm not sure if I still have this problem or not. When it was a problem, I started watching for my hard drive activity light to stop to make sure the update was finished before clicking the relaunch button. I still do that just in case the issue is still there.
-
andrew84 last edited by
Visual issues related to HW acceleration and CSS were ignored and still persist.
https://forums.opera.com/post/247686 -
vprofirov last edited by vprofirov
@treego is absolutely correct!
This is going on for years now.The 0.47.2-linux-x64 and the newest of the nwjs-ffmpeg-prebuilt are not working
This is waisting time of thousands of people every time, not to mention the new users of linux and opera, bashing their heads until they get lucky and find this forum thread or give up.
Luckily, we have the great opera community providing solutions, but no thanks to the problem creators/"developers".
It is time for the Opera-Linux devision to step up before users say to them selves enough is enough! This have happened in the past or did you forget?
@alexs 's solution is working for Opera version 79.0.4143.22 on Fedora 34 Workstation -> download libffmpeg.so
Reminder: substitute the existing libffmpeg.so in directory /usr/lib64/opera with the downloaded one and restart the opera browser
P.S. Thank you @alexs !