<SOLVED> Chrome 87 freezes after system upgrade on Sparky 6

[michal]

Hello everyone, and happy new year.
This morning I ran system upgrade, it went smoothly, no errors raised. However now, when I try to launch google chrome it freezes, if I start it from command line it says:

Code: [Select]

$ google-chrome
ERROR:sandbox_linux.cc(374) InitializeSandbox() called with multiple threads in process gpu-process.

I found someone already had similar problem

Code [Select]

https://askubuntu.com/questions/1230508/19141191410425-011526-129520errorsandbox-linux-cc374-initializesandbox unfortunately their solution

Code: [Select]

$ google-chrome --disable-gpu --disable-software-rasterizerer
did not help in my case, trying to launch google-chrome with parameters above renders an empty window with no url bar whatsoever.

Code: [Select]

$ google-chrome --version
Google Chrome 87.0.4280.141
cat /var/log/apt/history.log

Code: [Select]

Start-Date: 2021-01-08  08:59:39
Commandline: apt full-upgrade --no-install-recommends -y

Upgrade: python3-tk:amd64 (3.9.1-1, 3.9.1-2), build-essential:amd64 (12.8, 12.9), libatkmm-1.6-1v5:amd64 (2.28.0-2, 2.28.0-3), dialog:amd64 (1.3-20190808-1, 1.3-20201126-1), tzdata:amd64 (2020e-1, 2020f-1), libx11-xcb1:amd64 (2:1.6.12-1, 2:1.7.0-1), python3-lib2to3:amd64 (3.9.1-1, 3.9.1-2), libheif1:amd64 (1.9.1-1, 1.10.0-2), libkf5sane-data:amd64 (20.08.0-1, 20.12.0-1), hexchat-python3:amd64 (2.14.3-4, 2.14.3-5), libasound2:amd64 (1.2.4-1, 1.2.4-1.1), hexchat-plugins:amd64 (2.14.3-4, 2.14.3-5), firefox:amd64 (84.0-3, 84.0.2-1), hexchat:amd64 (2.14.3-4, 2.14.3-5), bash:amd64 (5.1-1, 5.1-2), libheif-examples:amd64 (1.9.1-1, 1.10.0-2), libatopology2:amd64 (1.2.4-1, 1.2.4-1.1), libasound2-data:amd64 (1.2.4-1, 1.2.4-1.1), libkf5sane5:amd64 (20.08.0-1, 20.12.0-1), libept1.6.0:amd64 (1.2+b1, 1.2.1), hexchat-perl:amd64 (2.14.3-4, 2.14.3-5), python3-distutils:amd64 (3.9.1-1, 3.9.1-2), libnetcf1:amd64 (1:0.2.8-1+b3, 1:0.2.8-1.1), firefox-l10n-en-gb:amd64 (84.0-3, 84.0.2-1), hexchat-common:amd64 (2.14.3-4, 2.14.3-5), intel-media-va-driver:amd64 (20.4.3+dfsg1-1, 20.4.5+dfsg1-1)
End-Date: 2021-01-08  08:59:52

How do I make google-chrome work again?
Thanks for any hints.

Kind Regards
M.

[runfox]

I am having the same issue with Chrome, but the update also made Slack (which i use for work) freeze (except in Rambox, Slack is working within Rambox) on my machine.

Also the whole entire LXQT DE freezes on me, KDE wouldn't even load it is just a black screen with the plasma logo in  the bottom corner, and I have to hard reboot & change the DE.

Now, I am rocking with XFCE, since only that and Open Box seem to work for me right now, without freezing. I also running the Liquorix kernel so I don't know if that is contributing to the additional problems I am having beyond Chrome.

[yosoyese]

Same problem here with Chrome... and Vivaldi.

[runfox]

Sadly, I need to distro hop, since the new update didn't fix this issue and nobody here seems to have any useful input. I need a functioning computer for work tomorrow, and don't have the time to truble shoot this. It's been fun sparky! I still run sparky on two of my laptops, but for my workstation I need to get this fixed before tomorrow morning.

[Murdock2525]

same issue. Frozen Brave and Chromium. I just timeshifted back a couple of days and will wait it out. MEGA sync quit on me a week ago so I installed it from the gnome software center. No problem. Same thing happened with Catfish file search.

[bin]

Does it show the same problem if you run chrome from the command line with  --no-sandbox at the end?

[michal]

Does it show the same problem if you run chrome from the command line with  --no-sandbox at the end?

Thank you for looking into it.
Yes, I have the same problem with  --no-sandbox, also since todays upgrade message is slightly different:

Code: [Select]

$ google-chrome --no-sandbox
[38999:38999:0111/094115.381266:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[38999:38999:0111/094115.416331:ERROR:shared_context_state.cc(74)] Skia shader compilation error
------------------------

Errors:

[38999:38999:0111/094115.420207:ERROR:shared_context_state.cc(74)] Skia shader compilation error
------------------------

Errors:

[38999:38999:0111/094115.545539:ERROR:shared_context_state.cc(74)] Skia shader compilation error
------------------------

Errors:

[38999:38999:0111/094115.833695:ERROR:shared_context_state.cc(74)] Skia shader compilation error
------------------------

Errors:

[38999:38999:0111/094115.835078:ERROR:shared_context_state.cc(74)] Skia shader compilation error
------------------------

Errors:

^C
What is interesting I am able to drive google-chrome with webdriver I only have the issue if I myself try to interact with it.
Another thing I noticed since todays upgrade is taskbar is not refreshed eg. clock has frozen I am also not able to click on the Menu/Start button.
BTW:

Code: [Select]

$ echo $XDG_CURRENT_DESKTOP
LXQt


[Luigi01]

Hi all,

Same for me, seems to be chromium related (so all browsers build on chromium, so chromium/opera/brave/...), also happened after recent update.
Diverted to firefox build browsers, which are not affected by this problem. Hope it can be fixed soon!

[paxmark1]

Chrome is not the same as Chromium.    Chromium is the Debian version of Chrome with some (hopefully most) of the Google non-free removed.

I do not have sparky repos on this computer, so I do not know the status of Google-Chrome on Sparky.   

Chromium has no debian candidate for testing - Buster - Sparky 6  at present.   Only Buster and Sid.

Via the BTS

Code [Select]

https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=chromium;dist=unstable

Code [Select]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972134
catches my eye,  There seems to be some progress.

Code [Select]

https://passthejoe.wordpress.com/2020/12/19/how-this-debian-stable-user-ended-up-with-google-chrome-from-googles-repository/
seems a fair assessment of the status of Chromium in Debian.

I do use Chrome at work, but it is on ancient LinuxMint or else on Chromebook.   

Others can research how to fix any problems with the Google download of Chrome.   I am off to work.

peace out.

[bin]

I have a Debian Testing VM - installed fresh Chrome 87 and it runs fine. No previous Chrome installed on that VM

Is it worth renaming the ~./config/google-chrome file and likewise the ~./cache/google-chrome and see if that helps?

[michal]

I removed ~./config/google-chrome and the ~./cache/google-chrome  but that didn't help. I start to believe it's a wider issue (or issues), especially that LXDE taskbar freezes so it's not just the browser.

[lami07]

Whatever is the reason for this behavior is already fixed in Sid. So it is just a matter of time for the fix to come down the pipe to debian testing repo.

[michal]

Brilliant, thank you for the update. I'll mark it <SOLVED> when the fix comes down the pipe. Out of curiosity is there a way to tell when that could happen (what's the timeframe days, months, unknown) ?

Meanwhile:
* Chrome still freezes - runfox suggests using XFCE, however I didn't find a workaround for LXQt.
* LXQt taskbar freezes when I start Menu -> Preferences -> LXQT Settings -> Monitor Settings a workaround is to use command line to manage settings, eg:

Code [Select]

https://askubuntu.com/questions/627320/put-external-monitor-on-the-left

[Luigi01]

After reading the latest replies: just installed the latest version of Chromium - runs perfect!

Also tested Opera and Brave: both also run ok again, however, the sandbox error remains - ??

[24194:24194:0116/184353.452738:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

So apparently the error causing them not to run has nothing to do with the sandbox. Oh, using Mate as desktop.

[Murdock2525]

No more issues here. Did a full upgrade via apt and then synaptic and zero surprises /