Introducing Opera 102
-
-
adam1709 last edited by
@thelittlebrowserthatcould I had previously enabled it in opera://flags, but this feature worked badly, so I disabled it. I read that it is supposed to appear in version 102 and I still don't see it. And normally in the settings I don't see this option.
-
thelittlebrowserthatcould last edited by@adam1709: Did you re-start Opera after enabling the setting in opera://flags? You are correct, it isn't shown in Settings with the flag disabled.
-
paul-durham last edited by
@olifant: As per a recent post of mine in the Opera Blog & in the Forums, Opera One feels far from production-ready. There are just so many serious failures. Aside from beings secure, the next thing users expect is that the product doesn't lose their tabs & information. @kornelia Mielczarczyk is the Product Quality & Launch Coordinator - please will you provide feedback on the wide-spread issues plaguing Opera One users, as well as Opera's plan to rapidly resolve them.
-
adam1709 last edited by
@thelittlebrowserthatcould Of course I then restarted. Whenever you change the flag it displays a message like this. I don't move the flag because it's probably still malfunctioning. It was supposed to be normal as I understood in version 102 as it was before version 100, and it isn't....
-
-
plovec last edited by plovec
@paul-durham: After the "Restart to update Opera to a newer version" I waited for 31 minutes while Opera incessantly worked on disk... I think you are right since I have all my speed dials restored.
-
paul-durham last edited by
@plovec: It is interesting to see others also had a very long delay before Opera opened after the update. This appears to be another issue with the stable release.
-
genegold last edited by
Win 10 Pro x64 22H2. 102 is not ready for release. It returned profile error message and then wouldn't start past 'O' sound screen. On reboot, 9 extensions either showed error or "maybe corrupt" messages. Had to run system restore.
-
-
raphaelbm last edited by
The announcement of 102 at https://blogs.opera.com/desktop/category/stable-2/#:~:text=Stable update
shows:
Stable
Introducing Opera 102
August 23rd, 2023However, 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.
Thx Raphael -
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 -
leocg Moderator Volunteer last edited by
@raphaelbm The version is on the title, 102. Since it's the first Opera 102 release in stable channel, the build number (102.0.4880.16) is not relevant.
-
tastodd last edited byTo 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.
