Posts made by vbnvbn

The issue remains with the newer 116.0.5366.35 version for linux.

Opera browser 116.0.5366.21 crashes and auto-restarts every time i click on the red 'O' button (Customize and control Opera).

The device is with an old embedded nvidia video adapter and the last version nvidia original driver (now it is also old).

What i know is that i had never had such an issue before this version of Opera was installed via apt update && upgrade.

The output at the very moment of crashing:

ERROR:elf_dynamic_array_reader.h(64)] tag not found
ERROR:elf_dynamic_array_reader.h(64)] tag not found
ERROR:elf_dynamic_array_reader.h(64)] tag not found
ERROR:elf_dynamic_array_reader.h(64)] tag not found

@vbnvbn said in Opera-stable 102.0.4880.16 gets stuck on launch:

Unfortunately, the latest version 104.0.4944.33 is bad - it runs very slowly.

Excuse me - i apologize. Actually 104.0.4944.33 works even better than 104.0.4944.28 - the issue turns out to be in the graphics drivers on one of the devices. Now everything works fine after a reinstallation.

@ondrejbenus said in Opera-stable 102.0.4880.16 gets stuck on launch:

Backlinking the issue on another forum with workaround that worked for me (disabling Qt) https://forum.artixlinux.org/index.php/topic,5847.0.html

Finally, that works for me - now opera runs on my devices with Debian LXQt again. Thanks for the reference.

Unfortunately, the latest version 104.0.4944.33 is bad - it runs very slowly.

Same old story with 103.0.4928.16 too.

@myswtest said in Opera-stable 102.0.4880.16 gets stuck on launch:

There are times when it seems all chromium-based browsers , when updated, render nothing, i.e., there is nothing shown in its window.

THIS IS the solution that works for everyone - keep in mind, this might NOT be the solution for your problem, but doing this will do no harm.

Open a command line window and execute this command

find ~/ -type d -name GPUCache

The list of files you see are simply cached data, that really doesn't matter ... however, for whatever reason, between version upgrades, they are corrupted.

So the easiest solution is to delete those - as I wrote, removing will do no harm. The following Linux command will delete all those , but if you prefer, rename that sub-directory to "GPUCache-backup" if you prefer

Reminder - this might be a long-shot solution for you, but it will not cause any issues - run this to clear:

find ~/ -type d -name GPUCache -exec rm -rf {} +

Hope it helps !

It doesn't work in our case because the issue is related to a basal incompatibility between the modern chromium-based browsers' GUI and GLib-GObject library in Debian 11 LXQt.

I don't know exactly where the issue comes from but now microsoft edge also gets stuck at launch in exactly the same way giving the same error output as opera in terminal.

same with 102.0.4880.56

@merlo1711
Try:
opera --force-device-scale-factor=x
where x can be a real number such as: 0, 0.5, 1, 1.7 etc.

@anindyasundarbhar
May this work for you too:
https://forums.opera.com/topic/42185/the-videos-don-t-play-topic/155?_=1694690044973

102.0.4880.51 also doesn't work for me.

@merlo1711
I found this link (as related to your issue):
https://forums.opera.com/topic/5343/faq-opera-s-whole-interface-is-too-big-how-do-i-fix-it

@merlo1711
Do you experience a bigger UI of other apps? - for example compare VLC to a KDE player. The UI of VLC and other apps is bigger than of others on my system - in some cases –– too big. I am also with a Qt-based desktop environment and Nvidia adapter with a proprietary driver (debian).

Upgrading to opera-stable 102.0.4880.46 is not yet resolving the issue.

@superflixla
Try these different versions of libffmpeg.so until opera start opening on your system:

https://github.com/nwjs-ffmpeg-prebuilt/nwjs-ffmpeg-prebuilt/releases

https://repo.herecura.eu/herecura/x86_64/

https://launchpad.net/~savoury1/+archive/ubuntu/chromium

In case you don't know how, find opera folder in /usr/ folder (with the command: find /usr/ -depth -maxdepth 10 -iname 'opera') and copy libffmpeg.so in it (that file should already be in that folder).

@merlo1711
What is your desktop environment (gnome, mate, kde, xcfe, lxde, cinnamon, deepin or antoher), your graphics card/adapter and the graphics driver you use?

@myswtest
The other chromium-based browsers work properly on the same configuration. Plus, opera browser had also worked properly for years on Debian/LXQt devices at my work until the moment when it was upgraded to version 102 few weeks ago. That is why i am not inclined to think that the issue comes from Debian distribution.

Upgrading to 102.0.4880.40 yesterday didn't resolve the issue in my case.

@ondrejbenus There had been no updates, except the one of opera, before the browser began to behave the way described in the OP. So the issue should come from the code of opera-stable browser version 102 - there had been no such issue with it on that system (with Debian 11 LXQt) before 102 was patched on 23 august during an upgrade procedure. 101 had worked well on the same device up to that day and hour (it still works well - already tested). I think it is most likely related to LXQt.

@lavanyadeepak-0 If other chromium-based browsers work flawlessly with the hardware acceleration option switched on, then find the appropriate libffmpeg.so version for you. Use these links:

https://repo.herecura.eu/herecura/x86_64/

https://launchpad.net/ubuntu/+source/chromium-browser

https://launchpad.net/~savoury1/+archive/ubuntu/chromium

https://github.com/nwjs-ffmpeg-prebuilt/nwjs-ffmpeg-prebuilt/releases