Posts made by sklunk

@leocg

I have the same issue. on 115.0.5322.119:
I click "Easy Setup", then "Themes Gallery" button, but no Christmas theme ....

@krasen @leocg

Thanks for the helpful replies. That's more than Opera has done to this point!

It's possible that my OS is not up-to-date, but Windows Updates are controlled by our I.T. department. I am still on Windows10 if that makes any difference.

I am still confused why 109 would work fine, then everything above that does not. Since nothing changed on my end that means that something had to change in the Opera code, or possibly the Chromium base, that is causing this to happen (BTW - I am also running the latest version of Chrome for comparison and it doesn't exhibit this behavior). That is what I am asking Opera to investigate.

I love this browser and have been a user since it's release in 1995 but the recurring problems since the move to Opera One are pushing me toward others. I am trying to stick with it though since it's still the fastest browser out there!

@bali505
It may have something to do with our firewall, but absolutely nothing changed on our end. Everything worked fine under 109.x, then when I installed 110.x it showed the behavior.

If you read my post I was running 109, updated to 110 and restarted (took about 5 minutes) and the behavior was there, then rolled back to 109 and restarted (another 5 minutes) and it was back to normal. Over the next few weeks I tried various 110.x, 111.x, and now this morning 112.x releases. Every single one of them exhibits the same behavior, but as soon as I go back to 109.x everything is fine. Since nothing changed in our firewall that tells me it's related to the Opera releases.

Well here goes my "normal" post for the last releases .....

And still no fix for the problem I have been having since the first 110.x version .....

Here is my previous post (which also includes the original post right after the first 110 release):

Opera:
Why have you not fixed the dns handshake issue i asked about many releases ago????

It has been present since the first 110 Stable release. Here is my original post:

Has anybody experienced trouble with pages loading on 110?

Yesterday I updated from 109.0.5097.80 to 110.0.5130.23. Although I am behind a corporate firewall, many sites that I went to minutes before the update would not work correctly after the update. Many gave me handshake failures and 404 errors related to CloudShare. Other sites loaded with strange formatting, and some would load but without images.

Like I said, the only thing that changed in those 10 minutes was updating Opera version. I rolled back to 109.0.5097.80 and everything is fine.

We are now 13 so-called "stable" releases since that post and still no fix!!

And here is my latest post in the 111.x thread .....

@leocg
Here is one example (just one, there are many more like this):
https://detroitwheelandtire.com

Fine in all 109.x versions, but doesn't work in 110.x, 111.x (and now 112.x since it was released this morning). Of course I can reload or click through to get to the page, but before 110.x it automatically loaded and I never got this error.

Ironically, here is another one that doesn't work:
https://forums.opera.com
(I had to roll back to latest 109 version to get logged in to make these posts!)

As soon as I roll back to 109.0.5097.80 then everything loads up correctly and immediately!

@leocg
Here is one example:
https://detroitwheelandtire.com

Fine in all 109.x versions, but doesn't work in 110.x, 111.x (and now 112.x since it was released this morning). Of course I can reload or click through to get to the page, but before 110.x it automatically loaded and I never got this error.

Ironically, here is another one that doesn't work:
https://forums.opera.com
(I had to roll back to latest 109 version to get logged in to make these posts!)

As soon as I roll back to 109.0.5097.80 then everything loads up correctly and immediately!

@leocg
Tons of examples, but I have rolled back to 109.0.5097.80 (that version doesn't exhibit the behavior).
I'll have to see if I can install the latest 111.x, get screenshots, then roll back again ....

And still no fix for the problem I have been having since the first 110.x version .....

Here is my previous post (which also includes the original post right after the first 110 release):

Opera:
Why have you not fixed the dns handshake issue i asked about many releases ago????

It has been present since the first 110 Stable release. Here is my original post:

Has anybody experienced trouble with pages loading on 110?

Yesterday I updated from 109.0.5097.80 to 110.0.5130.23. Although I am behind a corporate firewall, many sites that I went to minutes before the update would not work correctly after the update. Many gave me handshake failures and 404 errors related to CloudShare. Other sites loaded with strange formatting, and some would load but without images.

Like I said, the only thing that changed in those 10 minutes was updating Opera version. I rolled back to 109.0.5097.80 and everything is fine.

We are now 11 so-called "stable" releases since that post and still no fix!!

@leocg

Google Chrome does not exhibit this behavior. I have not tried any other Chromium-based browsers since they are not supported by my company.

I know the updates take time, but we are now 8 supposedly "stable" releases since the behavior started ...

Opera:
Why have you not fixed the dns handshake issue i asked about many releases ago????

It has been present since the first 110 Stable release. Here is my original post:

Has anybody experienced trouble with pages loading on 110?

Yesterday I updated from 109.0.5097.80 to 110.0.5130.23. Although I am behind a corporate firewall, many sites that I went to minutes before the update would not work correctly after the update. Many gave me handshake failures and 404 errors related to CloudShare. Other sites loaded with strange formatting, and some would load but without images.

Like I said, the only thing that changed in those 10 minutes was updating Opera version. I rolled back to 109.0.5097.80 and everything is fine.*

We are now 8 stable releases since that post and still no fix!!

@burnout426

Thanks for the suggestion but it was already turned off.
Just for fun I clicked it on, restarted Opera, clicked it off again, another restart. Still didn't change anything.

Well yet another 2 releases and still the same issue. And nobody from Opera has replied to my post or reached out to investigate. So much for customer support.

I am a long-time Opera user so I will try to keep using it, guess I'll just have to stay on V109 for a while ....

@leocg

See my post below from 8 days ago (same one I replied to).

Okay just installed 110.0.5130.35 and same exact issue.

Is anyone from Opera monitoring this? I have not received a single response to this issue!

Has anybody experienced trouble with pages loading on 110?

Yesterday I updated from 109.0.5097.80 to 110.0.5130.23. Although I am behind a corporate firewall, many sites that I went to minutes before the update would not work correctly after the update. Many gave me handshake failures and 404 errors related to CloudShare. Other sites loaded with strange formatting, and some would load but without images.

Like I said, the only thing that changed in those 10 minutes was updating Opera version. I rolled back to 109.0.5097.80 and everything is fine.

@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.

Does profile migration work correctly yet?!?!

Does profile migration work on this release? I am still on 101.0.4843.58 and it hasn't worked yet for me on ANY version of 102. Even the manual work-around posted here https://forums.opera.com/topic/65818/resolving-profile-loss-issues-in-opera-version-102-0-4880-16?lang=en-US&sort=newest_to_oldest doesn't work.

@neewuser

Thanks for posting this but it has already been mentioned numerous times. Also it only works 1 time -- once Opera updates you will need to do it again. However Opera has told me that they will have the flag to turn it off available in a soon future release (as well as a fix for the "O" menu rendering problem - finally!!)

@hexangst
Thanks for those helpful words added to this thread

Since Opera made the move to Chromium I have been using Vivaldi in parallel. It has it's problems too, but they listen to their users and beta testers. I still like Opera and would love to keep using it so I hope they get their "stable" release process straightened out. If I was really "done" I wouldn't take the time to post in these forums to try to get Opera to fix things ...

Well Opera, I give up ....

I have been an Opera user since a few days after it was released to the U.S. I have sung your praises on numerous occasions and even stuck with you through the move to Chromium (not a good move IMHO). But these latest problems with profile migration are killing me!

I went through all the pains these last few releases, but finally had 102.0.4880.29 working correctly. Then when I updated from .29 to .33 nothing migrated, so I followed the instructions about copying Default data over. That worked good for a few days, and now I saw .40 released. As soon as I upgraded - Bam! - no profile migration. So I went back to the blog post instructions for moving profile data, but this time it didn't work correctly. So no choice but to roll back to Version 101.

So now I have officially rolled back to 101.04843.58 and have all my data. I have synched my Opera account to make sure it all goes to the cloud, but as you know that doesn't capture everything. I have also deleted "opera_gx_splash.exe" to get rid of that annoying startup screen. It looks like I am stuck using 101 for a long time.

Even this one still has issues: "O" Menu button is not rendered correctly, Minimize/Maximize buttons do not work in Win10, you can't drag and drop bookmarks into folders, and a few other things. I have been living with these since they were just inconveniences, but how can you upgrade from 102.xxx.29 to .33 to .40 (all within version 102) and still not have profile migration working correctly. Once you have moved profile data shouldn't all subsequent 102 versions read from the same folders?!?!