Best posts made by gmiazga

We are currently investigating this issue and looking for a fix. We will release update as soon as we resolve the problem.

We have reverted to previous version of browser.js so problem should be gone soon for all users. Usually can take up to a few hours depending when was last update fetched.

Microsoft removed this detection. Their full reply:

We have removed the detection. Please follow the steps below to clear cached detection and obtain the latest malware definitions.

1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
3. Run "MpCmdRun.exe -SignatureUpdate"

Alternatively, the latest definition is available for download here: https://www.microsoft.com/en-us/wdsi/definitions

From our side there have been small changes in installer code on developer which probably got detected as malware together with Microsoft definitions update done on 2-3 October.

If you keep up to date with the latest security updates on macOS you might have spotted warnings about the Opera application being damaged on your system. This is related to how our update mechanism works. If you see this warning there is nothing to worry about. Unfortunately you will have to reinstall the latest version of Opera from www.opera.com. If you won’t reinstall you will be stuck with the older version and will be getting more of those warnings as autoupdate will try to execute but fail each time.

Some more background on this issue

When we perform updates they are first downloaded into $TMPDIR. One of the intermediary directories created during this process used to end with the .app extension. We download the update package to this directory and perform further operations on it.

It turns out that there was a security issue in macOS, which meant .app directories that didn’t contain an actual application could also have been used by malware to execute code outside of Gatekeeper. Apple released a security update that closes this loophole, as versions 10.15.7 and 11.3 of macOS, which were released this week.

The fix causes our intermediary directory to be detected as a broken application, and a system warning is displayed, blocking any operations on the content of this directory and breaking our update mechanism. The fix on our side is to simply use a different name for the intermediate directory.

If you would like to read more about this issue please head to https://objective-see.com/blog/blog_0x64.html.

@carlosjeurissen at the moment we do not have plans for closing our store. Will try to get some information about plans for allowing v3 in our store.

@jojo0587 fix for it is ready and should be available in next update. It's related to indexing of tabs not working correctly in chrome.tabs API when workspaces are used.

Hey, got a good news for you all. If you enable flag opera://flags/#dynamic-demuxer-selection issue should be resolved. It's still disabled by default in 54.0.2952.71 and will be enabled be default when 55 goes stable but you should be safe to turn it on now.

Hey, we have identified issue with crashloop which is related to recent adblock list update. Next stable update will include fix for this but we have also rolled back adblock list update until client with fix is distributed. If you have adblock enabled then you would have been affected by this issue. To fix this now you can force adblock list update manually but pressing upate button on following pages:

• opera://settings/adBlockerLists
• opera://settings/trackerBlockerLists

Hey, there is problem with one of oour certificates. We are currently in process of releasing client update as this can't be handled on server side currently.

Hey, we are currently looking into the issue with Windows Defender detecting .dll. All our Windows binaries before being published are scanned on VirusTotal. Version 73.0.3827.0 still shows no detections and binaries uploaded there are same like the ones on our autoupdate servers (few CDNs I checked at least) and FTP server.

We just released stable 72.0.3815.320 which includes earlier mentioned fixed for address bar issue. This will also be followed up by developer update 74.0.3870.0 later today and beta update later this week which were also affected by this issue.

@carlosjeurissen I got information that support for v3 in addons.opera.com has been scheduled for development. No ETA on it yet, so I will try to get this post update.

@adam1709: 85.0.4341.75 version includes fix for latest chromium 0-day (CVE-2022-1364). Was released to push it faster to all users. Changelog for 85 version updated to include this information.

It took way longer than expected but it's finally here. Changes have been deployed on production and it should be possible to upload extensions using manifest v3.

@adam1709: available to all systems. Got a slight delay with updating linux repositories. Should be live now.

Hey, we are aware that Chrome is dropping support for Windows 7 and 8 but we wanted to keeping those platforms updated as long as it wouldn't require lot of additional maintenance from our side. We will look into this as it didn't show up on our earlier tests before release.
For now we logged some GPU related crash on Windows 8 which is logged under DNA-104227

@alexs Thanks for noticing. It should be updated now.

Thanks, for reporting this is probably more of a browser issue than extension. Tracking it as DNA-82722.

So far we seem to have identified that there is indeed problem with Speed Dials being readded. This issue as far as we know is only affecting Windows 10 users after system updates. Mostly noticeable on Insider builds which get updates more often. We are currently working on a fix.

@edbj Thanks. We already have this fixed internally and will be available in next public update.