Opera 102.0.4880.51 Stable update
-
xb70 last edited by xb70
@xb70 Also, "migration?" Do you mean upgrading to the latest version by use of the word migration? Non-migrated profile? It sounds like I need an in-depth and detailed explanation of this whole migration process, with or without a "profile." Is a profile the same thing as synchronization?
-
Altmanm9943 last edited by
I would love an option to place the sidebar buttons on top of the bar instead of the bottom
-
Loraxz last edited by
With this latest update i have problems with the maximize and minimize buttons every time i open the browser. Windows 11
-
-
burnout426 Volunteer last edited by
"Profile" means all your browser data. As in, your settings, bookmarks, cache, history, cookies, passwords, everything. If you goto the URL
opera://about, you'll see a "profile" path. That's where most of your data is stored. You'll also see a "cache" path where your browser cached is stored.A dirty profile means one that's not fresh. As in, all your data isn't fresh like you just started using Opera. As in, you've been using Opera for a while for example. The longer you've used your data/profile and the more versions of Opera you've used with that profile, the more potential there is for corruption in your profile due to past bugs in the versions of Opera you used. Ideally, there should never be any issues with your data, but problems can crop up due to bugs. A lot of times, no amount of fixes in future builds can fix profile corruption.
If you ever wanted to start with a fresh profile (fresh data), you can wipe out all your data by deleting the profile and cache folders. You lose everything, but this can be a way to fix corruption if you suspect it.
None of that has anything to do with sychronization.
As for migration, starting with Opera 102, the layout of files and folders in the profile folder changed quite a bit. Quit a few files and folders had a new location in the profile folder. Instead of being in the root of the profile folder, they were in the "Default" folder. This was fine for fresh profiles. However, for existing profiles, Opera copied (not moved, so the originals were kept in their old spots) the files and folders from the old location in the root of the profile folder to the new "Default" folder. As in, Opera migrated the profile. This was done with the cache folder too.
However, because migration failed for quite a few users, those users had to downgrade to a version that didn't have the profile folder layout change so that Opera could use the copies of the files in the old location. Then, Opera disabled the file and folder layout change (disabled migration) for newer 102 builds so that users could user newer builds of Opera with the old layout that their profiles had. Migration is still disabled in this build in this blog post.
Opera has made some improvements to the migration that will hopefully fix things when it's turned back on. But, as a personal recommendation, I would keep regular backups of your profile folder just in case. And, as said above, if you've been using Opera for a while and used a version of 102 that tried to migrate your profile and failed, and then you downgraded to 101, and then upgraded to a 102 build that had migration disabled, you might have an issue with migration with it's turned back on. Hopefully not though.
Hope that helps. It's not something a normal user should have to worry about, ideally.
-
xb70 last edited by
@burnout426 Thank you so much! I was totally ignorant of of that. It sounds like one can use the later versions, if one knows how to copy and edit one's profile files appropriately, from a working version, in my case all the way back to 101....58, (oddly even though 102....29 through 46 were fine, only installation of 51 killed all the 102's, and I had to go all the way back to 101....58 to get my extensions back!). So I need to ID the relevant files in my profile now while it is working properly, save them someplace, then edit the profile of the latest version using copying in the files that I've saved from 101....58, in the appropriate places(s) in 102....51. But what can I expect to happen with the next version after 51?
-
burnout426 Volunteer last edited by
@xb70 said in Opera 102.0.4880.51 Stable update:
But what can I expect to happen with the next version after 51?
Not sure yet. Hopefully everything will just work though and hopefully Opera won't make the build available for autoupdate right away until users confirm things work right.
-
xb70 last edited by
There is quite a bit in the profile, many, many files! I have no idea which ones I would copy to exactly where (to the default file, as a folder, or what?) in a later version of Opera. Can you advise?
-
burnout426 Volunteer last edited by
@xb70 Are you saying you want to experiment? If not, there's no reason to mess with anything at the moment.
However, to see what files go where, just download Opera Developer and look at its profile and cache folder. Click options in the developer installer and make sure to disable "make Opera the default browser", "run at startup", and "import data from default browser". And, make sure the install path is "C:\Program Files\Opera developer" if installing for all users or "C:\Users\yourusername\AppData\Local\Programs\Opera developer" if installing for the current user. It won't interfere with your regular Opera.
-
karen-arzumanyan last edited by
If you press Ctrl+F to enter text, you can’t see where the cursor is.
demonstraion - https://imgur.com/Mr7WGXp -
-
sklunk last edited by leocg
@xb70:
The way burnout426 explained it is right on spot. Opera introduced the profile migration problem with version 102.0.4880.16 (the "first" move to version 102). It worked for some and not others through the next few releases. For me it didn't work at first so I rolled back to 101.0.4843.58 (the 101 versions kept the profile in the previous folder) which got all my data back. Opera eventually figured the problem out and posted instructions at https://forums.opera.com/topic/65818/resolving-profile-loss-issues-in-opera-version-102-0-4880-16?lang=en-US&sort=newest_to_oldest . When I went to 102.x.x.33 my profile didn't migrate again so I followed the instructions in that link and it worked. But then during follow-on 102 releases .33 and .40 I assumed my profile information was all moved over to the new locations so upgrading wouldn't hurt anything. But in both of those it didn't find the data and Opera treated me as a new profile, but for some reason when I followed the same instructions to manually migrate it didn't work for those 2 releases.So for now I rolled back to 101.0.4843.58 again and have all my data. Since then Opera has released builds 102.0.4880.46 and .51, so I keep asking if profile migration has been fixed before I upgrade. I like to keep the latest version of Opera but don't have the time to go through all the headaches of getting my data back. I am a (very) long-time user of Opera, and since my profile bounced back and forth during all the 102 releases, I probably have the "dirty" profile that burnout426 is talking about. Hopefully Opera finds a way to migrate old users and then keep that data in the correct folders moving forward.
-
suchmen last edited by
Still maximize button doesn't work at all, still splash logo appears with sound every start up, and still problems with wallpaper is reseted to default after every start up.
-
xb70 last edited by
Okay, I downloaded and installed 102....51 from the manual page where they are found, only to lose my extensions, I attempted to install 102...46 the last properly working one for me, then back to 102...29, and finally 101....58 which did have my extensions, only to have the automatic updating kick in (it never worked for me before!), so I knew that I was likely to have 102....51 again when I re-opened Opera today, BUT my extensions are back. What gives? Did going back to 101....58 make the auto update take my profile from 101....58? Or should I now wait for the auto-updating which folks had been bitterly lamenting which all of a sudden is now working for me. The good news is that my profile (my extensions) are back, after the auto updated Opera put in 102....51 in my case. Anyone?
-
xb70 last edited by
From earlier posts here, I find this fixup to the 102....16 debacle:
For Windows users
Copy profile folder without trailing \Default, the profile folder might look like this example (don’t copy this example): C:\Users\user-name\AppData\Roaming\OperaSoftware\Opera Stable
Open Explorer (Windows+E)
Paste the copied path and press enter to go to the profile folder
Find folder named Default and remove it.
Has anyone confirmed that this is the way to fix when migration doesn't work? -
tnts last edited byI was hoping you could fix the window not disappearing when I delete the last tab from an update a while back.
Now when I bring up a new window, the close window button disappears... -
Kuroodo last edited by leocg
God damnit. I was so glad to stay at Opera 99. Now because of this I have to upgrade to this stupid Opera One crap of an interface
-
-
Locked by
leocg
