[Solved]Opera 67.0.3575.31 freezing soon after startup

metaltrabant

metaltrabant @l33t4opera

@l33t4opera Thanks, tried, but it's still freezing. Resolved the kwallet issue though, but I think that was present before this problem appeared.

The main issue will be somewhere with these errors I guess:

"[920:1:0225/234506.590732:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[920:1:0225/234506.592328:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1873:1:0225/234508.986148:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[891:1:0225/234515.099843:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[1932:1:0225/234520.356869:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[1947:1:0225/234528.269767:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[1987:1:0225/234535.877741:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[1997:1:0225/234536.569890:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer"

l33t4opera

l33t4opera @metaltrabant

@metaltrabant I see. I would say it's rather not that, because I have the above errors on one of the boxes, but I don't experience this issue there.

You can try to launch the Opera with another switch "--disable-gpu-sandbox", and if it changes nothing, then with "--disable-gpu", and check if this helps.

Also, before trying the above, you can simply run the Opera with fresh profile (to check if the issue occurs also there), as follows: /usr/bin/opera --user-data-dir="/path/to/fresh/profile.

metaltrabant

metaltrabant @l33t4opera

@l33t4opera It's still freezing with both of those switches.

With a fresh profile, it starts fine, works fine, but in the terminal, throws the same errors:

[8804:8804:0226/000852.230974:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[8806:8812:0226/000853.018952:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018
[8976:1:0226/000853.530884:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[8996:1:0226/000853.583345:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[9021:1:0226/000853.669547:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[8804:8804:0226/000853.773064:ERROR:gles2_cmd_decoder.cc(8617)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glFramebufferTexture2D: <- error from previous GL command
[9102:1:0226/000854.786052:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[8777:8794:0226/000858.054091:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018
[9201:1:0226/000911.095481:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[9204:1:0226/000911.116550:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer
[9221:1:0226/000912.649054:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer

I guess it also doesn't help that my main profile has like 64 tabs opened, and more than a dozen extensions... so the issue can be anywhere, and it's already overloaded a bit.

l33t4opera

l33t4opera @metaltrabant

@metaltrabant Yes, it looks to be as I wrote above - those errors are not related to your issue. Perhaps you can try to test deeper with this fresh profile: open more tabs, close some, open more, install some extensions, and see if you can reproduce the issue under that conditions.

Alternatively, if you don't want to waste much of your time on testing, you can simply use that fresh profile: install your extensions there, copy/paste your "Bookmarks", "Web Data" and so on - don't copy "Preferences" and "Local State" (of course when the Opera is closed), and try to use it daily, instead of the old one, and see if the issue will be gone for good.

Small note: for the opened tabs, you can copy the "Current Session" and "Current Tabs" files.

metaltrabant

metaltrabant @l33t4opera

@l33t4opera The problem is, I wanna backup a lot of stuff from that old profile, so installing clean new extensions doesn't really solve my issue... I use the developer version now, that at least synced some of my stuff (including my opened tabs), and works fine.

Also, when I disabled extensions, one of those is The Great Suspender, and with that disabled, it didn't load my opened pages, just the pinned ones. So maybe I can narrow it down to those... but I think I'm done for tonight, thanks for your help so far If you have more suggestions, I'll gladly try them in the morning.

l33t4opera

l33t4opera @metaltrabant

@metaltrabant Yes, that way sounds also reasonable. You're welcome, and wish you good luck ;-)
I will try to find some time tomorrow, and check how it's going.

minho

minho

Same problem on two linux distributions here (Arch and Neon unstable).
Disabling synchronization solved my problem.
Opera synchronization is still almost useless and now it also is unusable.

metaltrabant

metaltrabant @minho

@minho Okay, but how do I turn off sync in the problematic browser that hangs in about 15-20 seconds after startup? Is there a startup switch to disable sync? (I tried the obvious --disable-sync, but that doesn't seem to work)

minho

minho

open opera
press alt+p to open preferences
paste "synchronization" in the search field
click on the button to disable synchronization

metaltrabant

metaltrabant @minho

@minho It was hard to do it fast enough, but eventually I got logged out of Sync, and yes, it seems to have solved the problem. In the meantime, someone replied to my bugreport from Opera, so I'll update him with this information.

Thank you so much for your help! Hopefully they'll find the bug within Sync, and I can use it again, it was working fine for me so far...

l33t4opera

l33t4opera @metaltrabant

@metaltrabant So it was the sync, which caused it in your case, nice to see it's resolved for you. It should be noticed by Opera's peeps, and investigated, and most probably improved (if not fixed) in one of upcoming versions.

minho

minho

Users affected by this problem can also disconnect from internet before open Opera, then disable synchronization in Opera settings.