Introducing Opera 102
-
sklunk last edited by sklunk
Well I just noticed a newer version 102.0.4880.29 on the ftp and offliner installer sites (timestamped 29-Aug-2023 13:41).
Who wants to be a guinea pig???
-
spike666 last edited by@sklunk I did it, everything is fine. Restarted Opera twice and my computer (Mac) once just to see that it was all there. I wasn't too worried, despite what some people say, the old profile is there even with the older 102 update. I did save all the profile stuff fresh just in case.
-
A Former User last edited by A Former User
@spike666 So did I just a moment before. There's no loss and no issue as it wasn't with the update to 102 before as well.
I really regret what happened to those that are rightly complaining as it seems. But there seem to be at least a silent minority or even majority that's fine. So am I.
Hopefully this new update fixes it for all. -
sklunk last edited by leocg
WooHoo - it seems to work!
I installed 102.0.4880.29 over top of 101.0.4853.58 without any problems. It moved all my data and everything works. You still get the silly "O" splash screen and noise, but you can disable that by deleting the "opera_gx_splash.exe" file (but you need to do this every time Opera updates).
Disclaimer -- As I have posted before, I am behind a firewall and use the offline installer. This is what worked for me. I have not tried Opera autoupdate so I don't know if that works or not.
-
-
kmara last edited by
@paul-durham Yes, lesson learned here, I will also export with each new set of research. Thanks again Paul.
-
letkin last edited by
Lost all my tabs and history, etc., in the update. How do I initiate the "rollback" noted in another post to try and get them back?
-
-
-
-
Bitul83 last edited by
Devs finally fixed the annoying issue on version 102.0.4880.16, I installed version 102.0.4880.29 manually over the older version 101.0.4843.58. Thanks a lot for the fix
-
xb70 last edited by
102....16 was bad, 102....29 was good, anyone on 102....33? I am reluctant to install it, without folks weighing in on it.
-
winblood last edited by
Is it just me or after some time of use, Opera slows down to a crawl, have to restart it...
-
-
xb70 last edited by xb70
Okay, I installed 102....33 on one computer--win 10-64, fully updated, FWIW. Seems fine. I examined every last setting, out of curiosity, and tweaked a few, basically locking the browser down. I did not test response time, however. But that computer is pretty old and slow, so it would only be relative to previous use. More later, after trying it on "the more important" Win 10-64 computer in the household. No sync issues.
-
-
xb70 last edited by xb70
Oops, installed 102....33 on the other computer and lost my extensions--again! Uninstalled and went back to 102....29 where they had been, not. Had to go all the way back to 101....58, but thankfully there were there. Yes, I was supposedly synced in the other two installations, but to no avail. I need to go up and find that link someone offered for syncing (power sync?).
It was kmara:
"Let's face it if they said, officially, 'Anyone encountering missing account settings and data can find it at [https://www.sync.opera.com/](link url) " that might have saved them the migration, but I agree with others that comprehensive flow testing in advance of release would have been the better option, then they would know to say that, or to prevent it from happening in the first place. It would have saved them a lot of migration." -
xb70 last edited by
Now the question is can I go forward to 102....33 to see if it has my extensions, having been reloaded in 101....58? No idea.....
-
burnout426 Volunteer last edited by
@xb70 Might be a good idea to turn of syncing of settings in Opera Sync for now just for good measure. One less thing for Opera to get confused about.
-
xb70 last edited by xb70
I was able to install 102....33 successfully upgrading on top of 101....58. It was already synced, apparently via 101....58. I am good now. 102....29 was successfully installed, but my first attempt upgrading on top of it failed, as it didn't sync properly, and wouldn't load my extensions, requiring me to go all the way back to 101....58 to find my extensions again. Ugh.
