Posts made by Opera-QA-Team

@rick2: Hi thanks for letting us know! We'll take a closer look into it.

@kilian01: Hi we tried the deb installation before the release could you please share what is wrong, as we haven't noticed that issue before the release.

@andrew84: Hi, thanks for the suggestion! We will think about it.

@sicu220: Hello, thanks for the reminder, the bug is awaiting fix.

@andrew84: Yes, I confirm, it seems like only Win10 is affected.

@rancor6: Hi, we know the issue, it refers to Win10 only. The bug is awaiting fix.

@rancor6: Hi, we know the issue, it refers to Win10 only. The bug is awaiting fix.

@kenedsf: Hi, we are aware of that. Thanks for reminding!

@krteq Hi please take a look at our latest stable release - we made sure opera for KDE is working correctly :))

@urby938: Hello, thanks for the reminder! We are aware of the problem and it's awaiting fix.

Starting the discussion

@andrew84: Hi, thanks for reminding. We are checking this. The problem is, it doesn't happen for everyone so we need to find the common point as we weren't able to reproduce it.

@kenedsf: Hi, thanks for the suggestion, we will consider it.

@andrew84 Thanks for pointing this out, we'll take a closer look!

Starting the discussion

@urby938: Hello, thanks for checking - we have no update regarding this issue so far.

@whisperer: Hi, thanks for sharing - the problem was reported and it's awaiting fix. : )

@ironbone: Hi, thanks for reporting. We already know the issue and it's awaiting to fix : )

@filbo: Thanks for checking the changelog so closely! The reason it looks this way is that 124 was our last stable release, so the changelog for 125.0.5729.x includes all changes accumulated since that last stable version, not only the fixes from the most recent 125 build.

Because of that, the changelog for 5729 shows a broader set of updates, it reflects everything from the previous stable release to the current one, which is why it may appear to repeat or include more items than expected.

Hope that clarifies things, and thanks again for keeping an eye on the details!

Hello everyone,

We want to share an important update regarding the recent issue affecting MV2 extensions.

A bug in the update rollout caused these extensions to become temporarily unavailable. This was not intentional, and we halted the rollout immediately once the problem was identified. Thanks to your quick feedback, we were able to catch the issue early. We truly appreciate your vigilance, support, and patience. We’re happy to let you know that we have now released a fixed version: 125.0.5729.15. This update restores proper MV2 extension support. We also want to reassure you that nothing has changed regarding our support for MV2 extensions. If we ever reach a point where we can no longer support them, we will communicate that clearly and in advance.

Thank you for your understanding and please let us know if you encounter any further problems.