Do more on the web, with a fast and secure browser!
Download Opera browser with:
Is that the correct changelog?
133.0.5910.0 – 2026-06-02
CHR-10241 Update Chromium on master to 147.0.7703.0
Certainly not. You now have two separate changelog entries for 133.0.5910.0 with different dates, and Chromium was already at 148.0.7778.97 in the previous build. 
(And Opera->About disagrees about that Chromium version as well.)
I used to be able to quickly disable ad or tracker blocking on a page by clicking on the "security" badge in the URL bar. That is, without manually managing exceptions in the settings.
Now, this badge is grayed out on all tabs and does nothing. Is anyone else seeing this? Is this a regression?
opera-developer 125.0.5727.1, on Linux Fedora F43 x86_64, installed as RPM (update) from the official repository.
@gmiazga: I don't know whether that was ever used. But anyway, CrashID=bp-2886acef-037e-41a6-9180-a593a0251105 and probably a dozen others.
@parduspars: Yes, almost immediate crashes here as well, on Fedora 43. I cannot tell which of my tabs triggers this.
Crash reports are automatically submitted, so I will just wait for an update.
Trying to export any page to PDF leads to crashing the tab (and all related tabs). This was already the case with the previous snapshot.
After updating to this version, each and every previously open tab crashes, and the log is full of
[159182:1:0714/134821.979265:ERROR:v8_initializer.cc(809)] V8 process OOM (Failed to reserve virtual memory for CodeRange).
(I have plenty of free RAM.)
Going back to opera-developer-113.0.5215.0-0.x86_64, and everything is fine again.
Linux 6.9.7, Fedora 40 x86_64,, GNOME on Wayland
@pirap2: And when you click on it (i.e. to see what it's good for :D) in a private tab, it says: "Aria is not available in Private Mode. Open regular Opera window to access the command line."
(It also doesn't react when I press either "Tweak it" or "Spell check" i regular windows.)
@leocg said:
@mbstafs That migration happened a few versions ago when Opera adapted it self to a change in Chromium's profile directory structure.
@leocg: Well, I, like many others, lost my custom search engines and my autofill history on the update from 108 to 109, so the data wasn't actually migrated.
I have now copied Web Data into the Default folder, and everything has re-appeared inside Opera 109.
@burnout426: Indeed, it seems the database "Web Data" hosting the custom search engines as well as e.g. the autofill data for your forms (and a lot more) was moved from "$CONFIGDIR/Web Data" to "$CONFIGDIR/Default/Web Data", without migrating the existing data.
I'm going to try copying the data over. If that doesn't work, I'll try to use an SQlite UI to manually migrate the relevant table data from the one database to the other. I guess that's what your instructions hint at, that a simple copy won't work.
Thanks for the hints.
@nashuim: So how do you add them again? Re-create them from scratch? I have too many...
@ralf-brinkmann: No, I am seeing this on Linux as well. I need to close those windows using the window manager (operating system), i.e. the windows' "X" button.
@iosaddict-0 said:
114.0.5720.4 is at least a month old.
So what?
To quote https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2721 :
"in Google Chrome prior to 113.0.5672.126".
(Replying to self) Sorry for nitpicking.
Aria wasn't a secret anyway, it announced in February:
https://blogs.opera.com/news/2023/02/opera-aigc-integration/
@leocg: I meant the Aria feature is in 100.0.4809.0. I checked and I have it.
Or is it server-side, and doesn't need to be integrated directly into the browser?
Or is it browser-side, and was developed all along, but never mentioned in the change logs to keep it "secret"?
@leocg: But it's obviously included, I even already tried it.
So, big announcement of Aria (integrated AI), and that comes on the start page when launching the update, but not a single mention in the change log (not in the detailed one either) - peculiar.
Anyway, I get the Aria announcement on the Opera "upgraded" start page as well, but the "Get started" button does: exactly nothing. Way to go! (On Linux x86_64.)
@iosaddict-0: If those fixes are in Chromium 114.0.5720.4 (as your link hints) , then very likely yes, because that release is the base for this Opera release. See the list of changes above!
@whataboutwolves I agree it should be there. I'm not sure I learned this keyboard shortcut in Opera, my experience may be from Firefox.
Ctrl+Shift+PgUp/PgDown has started working in Chrome for Windows only recently (it used to work on Linux for some time, apparently), and I welcome its appearance there. There also seems to be the F6, F6 key shortcut to enter tab selection mode, but I can't find this in Opera either.
Cheers,
gibson
@bonifacio: That's because you're using an alternative libffmpeg.so for multimedia support, and that doesn't support the requirements of newest Chromium. I mentioned it in this comment:
https://blogs.opera.com/desktop/2021/08/opera-80-0-4157-0-developer-update/#comment-260522
The libraries from herecura seem up-to-date, see if you can use those.