Introducing Opera 102
raphaelbm last edited by
The announcement of 102 at https://blogs.opera.com/desktop/category/stable-2/#:~:text=Stable update
Introducing Opera 102
August 23rd, 2023
However, the version is not shown. I have to go all the way to the changelog to discover the version is 102.0.4880.16
Please fix these announcements to mention the version at the same time as the announcement. You do this at Updates but not when announcing a new major level. Why do you do this? Stop it... Please be consistent.
This is a bug in the blog post. This is not a bug in the product.
younes-csm last edited by
let me join the crowd
I'm shocked that this update could be lunched in production in this state...
Making sure your tabs/profils/pwd etc... stays in place should be the first thing to check!
We need a fix/rollback immediately!
I went back to 101, with my internet off, on top of disabling autoupdate, and I got my tabs back.
2 hours wasted for an issue that isn't supposed to go unnoticed to the laziest of testers...
i love opera, not so much the last few (unnecessary, and now bad) updates
tastodd last edited by
To everyone who has problems with version 102 of Opera, I would advise you to roll back to 101, and then all passwords and bookmarks will return.
Apparently in Opera 102 there is a problem with accessing or specifying the address to the profile folder
burnout426 Volunteer last edited by
@renatob See https://www.reddit.com/r/operabrowser/wiki/opera/disable_updates_windows/. Easiest way would be to just block connections to the updater server.
Also see https://www.reddit.com/r/operabrowser/wiki/opera/rollback_version/ for how to roll back to a previous version.
burnout426 Volunteer last edited by burnout426
The data loss is probably due to the profile folder layout changes made to better match Chromium (which supports multiple profiles). In the profile path ("C:\Users\yourusername\AppData\Roaming\Opera Software\Opera Stable", there's now a "Default" folder (for the default profile) where files and folders specific to a profile (like "Preferences", "Bookmarks", "Login Data" etc.) go. Things that are for all profiles like the following files and folders:
browser.js CertificateRevocation Crash Reports default_partner_content.json GraphiteDawnCache GrShaderCache Local State MediaFoundationWidevineCdm MEIPreload opera_shutdown_ms.txt partner_speeddials.json Safe Browsing SafetyTips ShaderCache siteprefs.json WidevineCdm
, stay in the root of the profile path and do not go in the "Default" folder.
This change has been there in Opera Developer and Opera Beta for a while. It just now reached stable.
When you start with a fresh profile, all is good. When, you upgrade from a version without this profile layout change to a version with it, Opera copies your profile-specific files to the "Default" folder. For good measure though, Opera leaves behind the original copies at the root of the profile path. So, you'll actually have now-useless duplicates for some files and folders in the root of the profile path. However, as some of you have seen, those old duplicates come in handy if you need to downgrade to a build without the layout change. Otherwise, you could remove those duplicates if the upgrade went fine.
With that said, upgrading the profile to the new layout seems to work fine a lot of the times, but seems to fail other times as some of you have noticed. Downgrading and blocking updates is one solution for now. However, another solution might be to keep Opera 102 and:
Make a copy of the "Opera Stable" folder for a backup just in case.
Delete everything in the "Default" folder.
Move everything in the root of the "Opera Stable" folder that's not in the list above to the "Default" folder.
Also, in "C:\Users\yourusername\AppData\Local\Opera Software\Opera Stable", make sure your "cache" and "system cache" folders were properly moved to the "Default" folder.
Not saying that's a solution, but it could be a workaround for those that know what they're doing.
plovec last edited by
@burnout426 Thank's, I didn't notice the duplication of profile folder: that explains the 31 minutes I had to wait for Opera to restart (that's exactly the same time it took me to duplicate my profile folder before updating).
Since it's a looong time operation they should find a way to inform the user that Opera is working on something (some sort of dialog that says "Updating, please wait..."), instead of leaving it working in background without notice.
gmiazga Opera last edited by gmiazga
@plovec could you give us some details? 31 minutes seems like a lot of time for copying folder. Could you tell us what hard drive you have and size of different items/folders in your profile directory? Also are you using any antivirus or other software that could affect files copying? And what OS are you using?
A Former User last edited by
Rollout stopped. That was probably wise.
plovec last edited by
@gmiazga In my profile folder I have
and it's 3.89 GB in size.
The internal drive is this
and the OS is Windows 10 with standard antivir (Microsoft)
gmiazga Opera last edited by
We have currently disabled option to update to version 102 due to profile migration mechanism not working in some cases. It's still possible to manually download and install update.
@burnout426 mentioned earlier steps to finish migration manully. This is one time process and we are still investigating what could be causing issue.