Posts made by rick2

@andrew84 I did, I guess I missed that bit.

@Opera-QA-Team thaks for the respone, but I'm not worried about Stable (which I'll keep using as my main browser), just commenting that I'll stop (actually, I already have stoped) using Beta but don't want to switch to Developer as that is a bit too unstable for my taste.

Wasn't Beta discontinued?

So, that's why Opera Beta users like me were left out in the cold lately?
I mean, Stable is 125 whil Beta is still 124...

Guess it's time to move from Beta to another browser for me.

@MehrzadS the Opera flatpak is a community maintained package, Opera the company is not involved in updating it AFAIK.
At least that's what they told me a couple years ago and why I switched to using the RPM repositories instead.

@sopronman:
Funny thing, we have Opera Stable 125, Beta 124 and Developer 126

This version works on Linux (Fedora KDE) without crashing.

Something I noticed that's not related to this update is that lately Opera Stable and Beta won't end correctly. The windows close but "pgrep -c opera-stable" lists between 10 and 15 processes, and top shows one process consuming 100% of a core.

It might not be an Opera bug, it cloud be something on my system or my profile, it's just weird that it started to happen seemingly out of the blue.
I'll keep investigating when I can.

@Opera-QA-Team
Hello,
The new update 125.0.5729.15 is still broken on Linux under Wayland, it crahses and won't open.

$ kinfo
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.10-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics

Fedora KDE here, same issues as reported by others.

I downgraded manually but the broken update is still available in the repos:

$ LANG=C sudo dnf --disable-repo=\* --enable-repo=opera check-upgrade
Updating and loading repositories:
Repositories loaded.
opera-stable.x86_64 125.0.5729.12-0 opera

On Fedora KDE 43, this version of Opera Stable (124.0.5705.65) and also Beta 124.0.5705.51, fail to get focus when I click on a link in another app like kmail or akregator, i.e. the website opens but the browser remains out of focus.

Previous Stable didn't show this behaviour, neither did previous versions of Beta.

There's also another issue that Opera Stable and Beta recieve the Alt key in some circumstances. At first I though it was a problem of XWayland apps but it keeps happening with Opera working native Wayland (--ozone-platform=wayland).

Repro: open Opera, open Konsole, Alt+Tab to Opera, Alt+Tab to Konsole, use Alt+F4 to close Konsole, Opera recieves the Alt key and opens its menu.

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.8-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland

You should provide the update in the RPM repos to be more effective:

Available packages
opera-stable.x86_64     123.0.5669.47-0     opera

"Please note that a Linux build is unavailable for this release"

I'm kinda relieved and hope it's because you're trying to fix this annoying bug I reported on 124 Beta release:
https://blogs.opera.com/desktop/2025/11/opera-124-beta/#comment-395252

$ rpm -q opera-beta
opera-beta-124.0.5705.12-0.x86_64

$ kinfo
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz
Memory: 16 GiB of RAM (15.2 GiB usable)

Graphics Processor: Intel UHD Graphics

Hi!

I'm on Fedora 43 KDE Plasma, just upgraded to Opera Beta 124.0.5705.12.

The Opera window won't come to the front when I click a URL in another app, like Akregator (RSS reader).

Previous version did.
Regression?

Hello,

I was using Opera Beta and opened a lot of tabs, unfortunately it's a website that somehow made Opera use a lot of memory and it got killed by the OOM killer.

After reopenning Opera, only 2 of my 4 windows got restored, with no way of restoring them, nor any traces of the lost tabs in the history.

I only have a backup from last Sunday (6 days ago).
Is there any way to recover all those tabs from Opera itself or should I consider them forever lost and restore from the backup?

Browser info (translated from Spanish):

Opera One (version: 121.0.5600.12)
Updates channel :beta
System: Fedora Linux 42 (KDE Plasma Desktop Edition) (x86_64; KDE)
Chromium Version :137.0.7151.27

Hi @marinaz909

I don't know what changed exactly but after updating to Opera Beta 120.0.5543.29, Privacy Badger started working normaly in every site I tried.

Hi @marinaz909, sorry I haven't been able to make some time for this.

I do have several extensions active:

• Opera's ad blocker: Version 120.0.5543.12
• JSON Lite: Version 20.10.1 by lauri-rooden
• Privacy Badger: Version 2025.5.30 by efforg
• Reload Images: Version 2.5.2 by mubaidr
• RSS Detector: Version 2.0.2 by BS-Harou (Martin Kadlec)
• YouTube No Buffer - Stop Auto-playing: Version 0.4.6 by james-fray

I don't think I'll be able to test in the next few days, maybe next weekend.

I'll get back to you with my results.

Thanks again!

@marinaz909: Thank you!

Also, and this might be related, the Privacy Badger extensions seems to be non-functional on Opera Beta: it's icon in the address bar is greyed out and clicking it does nothing.

I reinstalled the extension and it kept trying to open its configuration page without success.

Hi,

Is anyone else experiencing ad blocking issues with Opera Beta?

Since the last update some websites started showing ads when previously they didn't, even after I disabled "Allow acceptable ads"

Some websites (like phoronix) even ask me to disable my ad blocker, only to immediately start loading (very obtrusive) ads.

This doesn't happen with Stable, only Beta with the last and this versions.

For those stil lstruggling with this, here's how I did it:

You have to enable the side panel and check the box to show Aria in it from the regular settings

Then from the side panel open Aria, got to its settings (icon in the top left corner of the side bar, settings button on the bottom), then you'll see what's in @burnout426 screenshot.

Uncheck the last item (writing mode shortcut) and then you can disable Aria and the side panel again from regular settings.