Opera 131.0.5877.74 Stable update

[Opera Comments Bot]

Opera Comments Bot last edited by

Hello! Opera 131.0.5877.74 is here, bringing a round of bug fixes: You can find the full list in the changelog. Happy browsing! Installation links:

Read full blog post: Opera 131.0.5877.74 Stable update

[Opera-QA-Team]

Opera-QA-Team Opera last edited by

Starting the discussion

[karen-arzumanyan]

karen-arzumanyan last edited by

The bug BUG-21893 is also present in version 131.0.5877.74.

[slim54]

slim54 last edited by slim54

endless installation, either through the browser itself or through a regular installation file. it started with the appearance of the update
131.0.5877.55 when updating from version 131.0.5877.24...
It's the same with 131.0.5877.74.
the only thing that helped was to go to the archive from the website with the versions and download from there.

[andrew84]

andrew84 last edited by andrew84

Split screen: Fixed crash on double-clicking the address bar

I thought it fixes the crash when clicking tabs in the address bar (because I saw the same rna in Developer's changelog ) but here in Stable it still crashing the browser.

Also, still crashing when using the tabs cycler (Ctrl+tab) while playing YT video.

[Sopronman]

Sopronman last edited by

By vertical tabs is tab jumping still here.

[Sopronman]

Sopronman last edited by

Horizontal tabs are OK, but verticals are always jumping. The same also by Developer version. Vertical tabs are in Chrome and Firefox without problems.

[stebot65]

stebot65 last edited by

When I press the tab island on the right side, to expand my addons, opera crashes every single time, after this latest update.

[thelittlebrowserthatcould]

thelittlebrowserthatcould last edited by

What improvement does the slower startup time exhibited over recent releases achieve?

[Opera-QA-Team]

Opera-QA-Team Opera @stebot65 last edited by

@stebot65: Thanks for letting us know. It is already fixed, the fix should be released with the new version.

[steeveboy]

steeveboy last edited by

Found a very strange bug... Opera crashes if you click this purple line here right after the extensions symbol...

[Opera-QA-Team]

Opera-QA-Team Opera @steeveboy last edited by

@steeveboy: Hi, yes, it's already fixed, will be released with the new update.

[Opera-QA-Team]

Opera-QA-Team Opera last edited by This post is deleted!

[andrew84]

andrew84 last edited by

his update fixes a crash that could occur when clicking the extension bar handle:

Why the crash in split screen is still not fixed.

[steeveboy]

steeveboy @Opera-QA-Team last edited by

@opera-qa-team: Thank you very much for the quick fix and update! I appreciate it! Already downloaded Version: 131.0.5877.97 fromt FTP-server. Great job, it's fixed. It collapses as it should without crashing. Have a great and sunny weekend guys!

[Sopronman]

Sopronman last edited by

Tab jumping is still here, also by the newest 131.0.5877.97 version.

[albano23]

albano23 last edited by albano23

The stable versions of Opera 131, from version 54 to the current one ending in 97, have several serious bugs in their snap (Ubuntu 22.04.05 LTS in my case) that should be fixed: 1) They fill the GNOME logs with thousands of messages with the error "Invalid RE2 repetition size, invalid perl operator"; 2) This causes a large amount of disk space to be consumed in a single session, as can be seen with the commands sudo journalctl --disk-usage and sudo ls -lh /var/log/journal/*/*.journal; and 3) In version 74, a very serious error occurred when updating the chromium-ffmpeg snap: "at least file with resources (.pak) is corrupted, please reinstall opera". Luckily, shutting down and restarting my PC fixed it for me. // In version 131 ending in 24, none of these bugs were present. I don't recommend using sudo journalctl --vacuum-time=1d to fix the issue of thousands of messages mentioned in point 1, because it could break your current session. I would like these problems to be reviewed by both you and the Snap Opera packagers. I hope all these issues will be resolved in version 132, which will use Chrome's 148 engine.

[steeveboy]

steeveboy last edited by leocg

Hi Opera team,

i just had a chat with ChatGPT and it thinks it has to be an Opera Problem (focus lost when starting a new private window from taskbar right click Opera then "New private window"). If you cannot reproduce it at all, it's alright. It happened to me by upgrading to version 131. If on your system everything's fine, then I'll wait for a Microsoft cumulative patch, see if this fixes the broken focus handling. So if that's the case, never mind. Just wanted to mention it after asking ChatGPT for a text which I can copy-paste for you devs. Maybe it helps, if not it's ok. So the following is the text from ChatGPT...

I found a reproducible focus issue with private windows on Windows 11 and wanted to provide a clean reproduction case.

Environment

• Opera One: version 131.x
• Windows 11
• Issue reproducible consistently

Problem

When opening a private window via the Windows taskbar jump list:

Right click Opera taskbar icon
→ "New private window"

the new private window opens correctly, but the address bar / omnibox does NOT receive keyboard focus.

Result:

• typing immediately after opening does nothing
• user must click the address bar manually
• sometimes TAB or CTRL+L restores focus

Important observation

The problem ONLY occurs when launching the private window from the Windows taskbar jump list.

The following methods work correctly and DO focus the omnibox:

Works correctly

Keyboard shortcut:

Ctrl + Shift + N

Direct command line launch:

opera.exe --private

Opening private windows from inside Opera menus also appears to work normally.

Additional testing already done

The issue persists after:

• creating a fresh Opera profile
• disabling extensions
• disabling hardware acceleration
• restarting Windows
• reinstalling Opera

So this does not appear to be profile corruption or an extension issue.

Likely cause

This looks specifically related to:

• Windows 11 taskbar jump list integration
• AppUserModelID / ShellExecute launch path
• missing focus handoff to the omnibox after private window creation

The direct opera.exe --private launch path works correctly, which suggests the bug exists specifically in the jump-list-triggered private window handler.

Hope this helps narrow it down.

[steeveboy]

steeveboy last edited by leocg

Opera One 131.x on Windows 11 (HDR is always ON):

I found a reproducible YouTube video rendering bug related to hardware acceleration.

Issue

While watching YouTube videos, opening UI overlays (especially the notification bell/menu) causes the video black levels / gamma to briefly change:

• video becomes brighter for a moment
• then returns to normal

This only happens with hardware acceleration enabled.

Important findings

• Disabling hardware acceleration completely fixes the issue.
• Disabling MPO (Multiplane Overlay) does NOT fix it.
• Enabling Lucid Mode stabilizes the video completely.

Current workaround:
I enable Lucid Mode permanently on the lowest setting (Level 1/5). With Lucid Mode active:

• black levels stay stable
• no brightness/gamma flicker occurs
• opening YouTube notification overlays no longer affects video rendering

This strongly suggests the issue is inside the Opera/Chromium GPU video rendering or HDR/tone-mapping pipeline, possibly related to compositor repainting during UI overlay updates.

The Lucid Mode workaround may help narrow down the rendering path involved.

[leocg]

leocg Moderator Volunteer @steeveboy last edited by

@steeveboy Couldn't reproduce it here in Opera One Developer. Opening a private window using the right click menu on the task bar doesn't make the focus to be out of the address bar.