Opera 79 Stable
-
-
burnout426 Volunteer last edited by burnout426
@hectormaciasa1979 Note that checking for updates on
opera://aboutandopera://updatedoesn'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 !
-
-
vprofirov last edited by vprofirov
@pinheadlucas check and try @alexs 's solution, before you replace the existing file you should make a backup of it.
If it works - repost, so other users with Linux Distro like yours - know
-
-
A Former User last edited by
@alexs - That version of ffmpeg requires C version > 2.27 so Opera won't load on Ubuntu 18.04 Lts
-
davidr last edited by davidr
I have the same problem as reported by @johnd78 and others. It happens like this: after Opera has been running for a few minutes (not immediately after a program or system restart, but some time later), whether in a new or existing tab, if I click in the address/search bar, type, and press Enter, nothing happens. It doesn't matter whether I type a search string or a Web address known to be valid: nothing happens. The typing appears dimmed as I type, and there is a globe icon at the left of the bar. Switching to a different tab and then back to the non-functioning tab sometimes heals the problem and sometimes does not. The problem does not happen in a newly opened window. This bug has been around at least since last November; besides the forum thread @johnd78 links to, see https://forums.opera.com/topic/44882/solved-address-search-bar-doesn-t-work-won-t-let-me-enter-grays-out-text-etc/175.
I am using Opera v. 79.0.4143.22; as far as I know this is the stable version, since I don't use Opera betas. I am on Windows 7 Pro 64-bit SP1.
-
chas4 last edited by@leocg I see it in all 3 channels for a few years now.
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. -
chas4 last edited by
@burnout426 On a SSD here (pre NVMe drive), the relaunch button should not show until after it is ready to restart to finish the update
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. -
styen last edited by styen
There are some scripts to fix ffmpeg and widevine on linux (Debian-based) based on https://github.com/nicolas-meilan/fix-opera-linux-ffmpeg.
Main branch. Currently works fine:
https://github.com/Ld-Hagen/fix-opera-linux-ffmpeg-widevine
Testing branch allowing to create auto-fix hook for apt (hope to get feedback if it works or not):
https://github.com/Ld-Hagen/fix-opera-linux-ffmpeg-widevine/tree/lazy -
mikerobinson last edited by
A lot of pages just flat-out crash for me now, such as Gmail and Facebook.
-
mikerobinson last edited by
@mikerobinson: Ok, I reinstalled Opera and now it's working again. Who knows what happened last time...
-
mikerobinson last edited by
@mikerobinson: Ok, I reinstalled Opera and now it's working again. Who knows what happened last time...
-
GKaczmarek Opera last edited by
The address bar bug was reported as DNA-95481. Thanks a lot to all of you that provided us with information that helped us track it down
-
davidr last edited by
@gkaczmarek said in Opera 79 Stable:
The address bar bug was reported as DNA-95481. Thanks a lot to all of you that provided us with information that helped us track it down
Thanks, that's great to hear! Looking forward to the fix.
-
andrew84 last edited by
I have performance issues since 79 version when watching youtube using avc1 codecs (even without the animated tab indicator). It's fine in 78.
I also checked in Edge Canary and no issues there. -
A Former User last edited by
@treego: I got tired of using Opera on linux, even today they don't support libffmpeg.so (ie they don't support H.264 format natively). I think this is absurd. After this update that prevented me from watching videos from youtube, twitter and other sites, I decided to switch to Brave browser.
