Opera-stable 102.0.4880.16 gets stuck on launch
-
ondrejbenus last edited by
@vbnvbn Not sure why, but I didn't think about installing an older version. Really works, Thanks for saving me.
For others, you can download an older working version from https://get.opera.com/ftp/pub/opera/desktop/101.0.4843.58/linux/
Or pick your favorite version here: https://get.opera.com/ftp/pub/opera/desktop/ -
sorenfeodor last edited by
I have now successfully installed 102.0.4880.40 on Linux Mint 21.2 from deb. I have not changed anything (same extentions as when updating failed 14 days ago), but of course a number of other packages have been updated in the previous 14 days. I have not tried to install opera-updates since 102.0.4880.16 gave me problems.
-
-
myswtest last edited by myswtest
If you haven't already, you should post the issue in a Debian forum ... most likely related to the/your Deb environment.
No probs here on openSuse Tumbleweed, using a Flatpak.
-
vbnvbn last edited by
@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. -
-
-
-
-
vbnvbn last edited by
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.
-
myswtest last edited by
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 GPUCacheThe 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 !
-
vbnvbn last edited by
@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 GPUCacheThe 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.
-
-
pindos last edited by@vbnvbn said in Opera-stable 102.0.4880.16 gets stuck on launch:
the issue is related to a basal incompatibility between the modern chromium-based browsers' GUI and GLib-GObject library in Debian 11 LXQt.
Maybe you have to inform the developers of LXQt-environment about this bug? The latest version of Opera works fine on Debian 11.7.
-
myswtest last edited by myswtest
@vbnvbn said in Opera-stable 102.0.4880.16 gets stuck on launch:
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.
So, it works using Cinnamon (mentioned by @pindos) on Debian. (and my environment: Tumbleweed using KDE Plasma).
But I agree, seems an obvious issue with this particular LXQT implementation on Debian, especially since other Chromium based browsers are affected.
A quick test would be to login using another DM, then launch Opera.
-
ondrejbenus last edited by
Backlinking the issue on another forum with workaround that worked for me (disabling Qt) https://forum.artixlinux.org/index.php/topic,5847.0.html
-
myswtest last edited by leocg
@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
So as with this - add this to the launch settings (?):
--disable-features=AllowQtI read thru that thread - that's an easy fix, but I read others found more involved fixes.
And I see the issue is reported by a number of LXQT users, but one instance of KDE.
Some folks solved it by running XFCE (mostly as a test, which I suggested),
It appears to be an issue with QT, so yea, folks who use LXQT will mostly be affected. (though some did a workaround with gtk settings).
So Not an Opera issue, as the OP alludes to.
-
vbnvbn last edited by
@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.
-
vbnvbn last edited by vbnvbn
@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.
-
Locked by
leocg
