Can't open private window from taskbar icon

[Marri]

Marri last edited by

I agree with you both - this problem is present for quite a few months and no fix is to be seen...
Unfortunately, there are two options - one, there is some particular corrupted setting, which cause Opera to fail to start in private mode, or two, the synchronization itself is corrupted.
In the first case, simply changing one setting would be sufficient to fix it (but which one is creating this synchronization error?) and in the second case, disabling the synchronization is the only option for now (and let's be hones, how often do you change your Opera setting? - I personally set everything as I desire and stay with it, but I understand that some may not be as steady with it as I am).

[yorgosfzs1]

yorgosfzs1 @Marri last edited by

@marri Interesting to note that launching private mode from the taskbar hangs whereas launching it from within the browser works fine. Seems that sync needs the normal mode first, then works in private as well. Anyway, not a big issue for me but rather a convenient option to have to avoid the extra step. Hopefully somebody we'll pay attention and we'll get it back in the next build(s).

[burnout426]

burnout426 Volunteer last edited by

With Opera 111.0.5168.25 64-bit, with Sync enabled (syncing everything), on Windows 11 23H2, while Opera is closed, when I right-click Opera's pinned taskbar icon and choose "New private window", Opera opens in private mode and everything is fine. No freezing or anything.

Few things you can test though. One would be to disabling just syncing of settings instead of disabling Sync altogether to test if that helps.

There other would be:

While Opera is closed, hit Windows key + r to open the run dialog, type cmd and press enter to open a command prompt.

Then, type:

cd "%LOCALAPPDATA%\Programs\Opera"

and press enter to get to Opera's install folder (assuming you used the default current-user install in the installer's options).

Then, type:

opera --private --enable-logging --v=1

and press enter to start Opera.

When Opera freezes, you can kill it however you usually do (and hit ctrl + c in the command prompt to kill the logging if needed). Then, you can type:

notepad "%AppData%\Opera Software\Opera Stable\opera.log"

and press enter to open the log file in Notepad.

You can then look through the log file (might be long) to see if there's anything interesting in there as to why Opera froze).

[Marri]

Marri @burnout426 last edited by

@burnout426 I have tested disabling just syncing of settings - when I turn that particular one off, without changing anything else, it starts without any problems. Overall, interesting idea, but one does need specific skills to read log files, which I personally do not posses.

[Marri]

Marri @yorgosfzs1 last edited by

@yorgosfzs1 I certainly do hope for the same thing as you!

[yorgosfzs1]

yorgosfzs1 @burnout426 last edited by

@burnout426 I've followed the guide and got some errors in the cmd prompt when Opera launched (see below) and saw some runtime warnings in the log file. I also saw a bunch of invalid rules referring to websites? The log file is 760 lines long so I'm not sure if I can spot the problem with my untrained eye.

Errors from CMD

C:\Users*****\AppData\Local\Programs\Opera>[22564:22556:0613/092255.051:ERROR:url_pattern_set.cc(287)] Invalid url pattern: chrome://startpage/
[22564:22556:0613/092255.052:ERROR:url_pattern_set.cc(287)] Invalid url pattern: chrome://startpage/
[22564:22556:0613/092255.054:ERROR:url_pattern_set.cc(287)] Invalid url pattern: chrome://startpage/
[22564:15148:0613/092255.081:ERROR:partner_bookmarks_utils.cc(270)] Unable to read partner speeddials file.

Warnings from log:

[22388:10228:0613/092255.616:WARNING:runtime_features.cc(730)] AttributionReportingCrossAppWeb cannot be enabled in this configuration. Use --enable-features=ConversionMeasurement,AttributionReportingCrossAppWeb in addition.

[burnout426]

burnout426 Volunteer @yorgosfzs1 last edited by

@yorgosfzs1 If you want to upload the log file somewhere and link to it, someone can take a look.

The cmd errors you posted are probably not related.

[burnout426]

burnout426 Volunteer @Marri last edited by

@marri Just for good measure. what other Operas were you syncing settings with?

[yorgosfzs1]

yorgosfzs1 @burnout426 last edited by

@burnout426 thank you, here is the link to the file: https://mega.nz/file/lo9wzbTB#kqv4BMqAWfdsQ9S49RWjHbM0jZJyJl1eQ0vSxYVc1T8

[yorgosfzs1]

yorgosfzs1 @burnout426 last edited by

@burnout426 I have 3 Windows 11 machines with the same Opera One installed. The Windows version on all is Windows 11 Pro 23H2 (Insider's build 22635.3720), The Opera is 110.0.5130.82

[burnout426]

burnout426 Volunteer @yorgosfzs1 last edited by

@yorgosfzs1 Asked someone to look at it. Please keep the download available for a while.

I looked at it and don't see any errors that I think are related. I do see lots of invalid rule errors for the adblocker though. I don't think that's related and not sure if those are synced or not. But, if you want to test, you can totally disable the adblocking and tracking protection at the URL opera://settings/privacyProtection to test if that avoids the freeze. If not, you could further test by clearing any rules you've added for sites etc. to test if that helps. But, not sure if you'll want to do that.

[yorgosfzs1]

yorgosfzs1 @burnout426 last edited by

@burnout426 Thank you for helping with this. I did turn off adblocking and tracking but didn't help. The only thing that worked so far is turning off sync for settings. Thanks again for your help!