Opera 123.0.5669.47 not running with macOS 11.7.10 Big Sur
-
speedtolosa last edited by
I use an old MacBook Pro (end of 2013) with Intel Core I7 processor, and running macOS Big Sur 11.7.10, last masOS version allowed on this hardware.
Currently running Opera 122.0.5643.92, the last update automatically installed (123.XXXXX) is not compatible with macOS 11.7, so each time I restart Opera, I have to reinstall the 122 version....
How an incompatible update can be automatically installed without any control of the OS version ?
Is it possible to stay with my current 122 version ?Thanks for your help
-
burnout426 Volunteer last edited by
Yes, 123 is based on Chromium 139 that dropped support for macOS 11.7.
With that said, I reported the issue with 122 updating to 123 on 11.7. Hopefully Opera can fix things to block it.
For now, you can try blocking Opera's update servers in your etc/hosts file. Then, do
sudo dscacheutil -flushcachein a terminal to flush your DNS.You can see if you can find an autoupdate file in /Applications/Opera.app/Contents/MacOS/ and delete it.
You can try doing:
defaults write com.operasoftware.Opera OPDisableAutoUpdate truein a terminal, but don't know if that will work or not.
You can create a shortcut to Opera that uses:
/Applications/Opera.app/Contents/MacOS/Opera --disable-updateand always use that shortcut to start Opera.
You can try adding:
export OPERA_AUTOUPDATE_DISABLED=1as an enviroment variable. See https://www.google.com/search?q=macos+add+environment+variable for more info.
-
speedtolosa last edited by
@burnout426 thank you for your help, it's OK with the command line "defaults write com.operasoftware.Opera OPDisableAutoUpdate true" !
-
-
MainHancho last edited by
@burnout426 I deleted the autoupdate file in /Applications/Opera.app/Contents/MacOS/
and now every time i check for an update it says it is the latest version.
is there a way to make it able to update again?
-
burnout426 Volunteer last edited by
@MainHancho If you delete the autoupdate file, that will break checking for updates. But, that should be OK since there won't be any new versions for 11.7.
If you want to check for updates again, you need to restore the autoupdate file and undo any other things you did to disable/block updates.
If you don't have the file anymore, you'd need to reinstall Opera.
-
fleerp last edited by
@burnout426 Howdy! Along the lines of preventing auto-update but more basic...
Opera on mac was my #1 browser until, a few days ago, mid-session, auto-update put it beyond my imac's osx capabilities. I'm on osx 11.7.10, as well. (Don't want to go back to chrome or safari!)
** Besides attempts to prevent the auto-update, do you (or does anyone) know where I can download the mac version prior to the Nov. 6th (2025) update (or earlier, I guess) that's still operational with osx 11.7.10?
Thank you in advance!!!!
-
burnout426 Volunteer last edited by
@fleerp Should be https://ftp.opera.com/pub/opera/desktop/122.0.5643.150/mac/.
-
fleerp last edited by
@burnout426 Thank you! I'm not sure which link is the one I'm looking for, though...2nd from the bottom? Not sure what the autoupdate links are...thank you!!
-
-
fleerp last edited by
@burnout426 Thanks! I just did and installed it. I get a message when I try to open it saying "Opera.app is damaged and can't be opened. You should move it to the Trash." - then my only options are 'move to trash' or cancel.
Never seen a message like that before, have you?
Thankyee once again!
-
-
burnout426 Volunteer last edited by
@fleerp You can open up a terminal:
cd ~/Downloadsand then:
shasum -a 256 Opera_122.0.5643.150_Setup.dmgto make sure you get:
aec89aee6a68ebf0c5ffad30d0929f9f5208282326c23ddc5941bfe97862240f -
burnout426 Volunteer last edited by
You can try the previous build https://ftp.opera.com/pub/opera/desktop/122.0.5643.142/mac/.
-
fleerp last edited by
@burnout426 ah it's my fault. before opening the fresh install, i renamed the 'opera_autoupdate' file inside the mac os folder (inside view package contents) to try to prevent it updating upon opening. But my messing with that file causes the previously mentioned move to trash message. So now I'm trying to figure out another way to disable it.
Ah, the joys of not having a newer computer.
(sorry for the delayed reply - I've got the message on here saying as a new user I can only post every 600 seconds. ha!)
