Google Chrome not working after update

English Applications
#1

Todays update (Kernel, Chrome…) made Chrome starting up, but not connecting. Console gives:

vos@linux-urgh:~> google-chrome-stable
[4847:4847:1019/042815.133389:ERROR:sandbox_linux.cc(346)] InitializeSandbox() called with multiple threads in process gpu-process.
[4772:4806:1019/042815.265458:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1019/042815.265599:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[4772:4806:1019/042815.323627:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1019/042815.323767:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[4772:4806:1019/042815.372821:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1019/042815.372901:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[4772:4806:1019/042815.923608:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1019/042815.923737:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[4772:4806:1019/042815.945419:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1019/042815.945535:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[4772:4806:1019/042815.969599:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1019/042815.969709:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1
[4772:4806:1019/042818.154661:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child
[5:5:1019/042818.154782:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1

Found the same error back in 2015 with CENTOS.
Chrome is working, if it is started with: google-chrome-stable --no-sandbox

Somebody noticed the same?

#2

I have the same error (openSUSE Thumbleweed)

#3

Same error in leap 42.3

#4

It was something that changed in Chrome 62 because I had this same issue when google-beta was updated to 62. I switched to chrome-stable which was still at 61 hoping that the issue would be resolved before the stable version was updated. Obviously that didn’t happen.

If you run with the option --no-sandbox it seems to work ok.

#5

I have the same issue on the Tumbleweed as well. Similar issues have been reported a while back in the following:

https://bugs.chromium.org/p/chromium/issues/detail?id=512561
https://bugzilla.redhat.com/show_bug.cgi?id=1317171
https://bugzilla.redhat.com/show_bug.cgi?id=1251996

As was already noted, if you start the latest google-chrome stable (RPM google-chrome-stable-62.0.3202.62-1.x86_64.rpm) with --no-sandbox command line arg the issue goes away, but you probably don’t want to run it this way.

I failed to make it work with SELinux manipulations described in the links due to my lack of knowledge and time. So I ultimately had to downgrade to the previous
release of google-chrome (stable) (google-chrome-stable-61.0.3163.100-1.x86_64.rpm) and the issue disappeared.

Unfortunately Google does not maintain a public archive of previous Chrome releases, but you can find it here: http://orion.lcg.ufrj.br/RPMS/myrpms/google/
Packeges from the site pass the signature test.

Hope this helps,
-Azary

#6

I’m having this problem on my Desktop PC with google-chrome 62.0.
But I’m NOT having it on my Notebook with both google-chrome-beta 62.0 and google-chrome-unstable 63.0 !
Both are on openSUSE-Tumbleweed.

This is strange.

#7

Thanks for feedback.

I can confirm this. This version of Chrome is working well with Ubuntu 16.04.02 LTS and with the laptop leap 42.2.
With the desktop leap 42.2 it gives the error from above, weird.

#8

I’m suffering from this too, on Leap 42.2. I was about to install 42.3 but that doesn’t seem to be a solution.

I’m not keen to run without a sandbox, although that does work.

A bit stuck as to what to do next. Someone posted a link to a Chrome RPM archive but I don’t know how to test the signature of an RPM from an unverified source.

#9

How do you apply the signature test?
Thanks

#10

Same problem for me on Leap 42.2 and Chrome 62. Running with no sandbox works.
I have also installed Chromium 61 which works fine, however doesn’t work with Netflix.
I am not particularly keen on running without the sandbox. Hope a fix comes from Google soon. For regular browsing I use Vivaldi.

#11

I think this is a new issue, and not the older SELinux issue. The Chrome developers seem to have a fix for it and will be patching it soon. A better option over the --no-sandbox is --disable-namespace-sandbox (This option doesn’t give a security warning)

More information can be found https://bugs.chromium.org/p/chromium/issues/detail?id=776359

#12

I don’t use Chrome/Chromium or netflix but afaik for netflix to work on Chromium based browsers you’d need chromium-plugin-widevinecdm from packman it’s not installed by default and Chromium can not use Chrome’s plugins
http://packman.links2linux.org/package/chromium-plugin-widevinecdm
if you have packman just do

zypper in chromium-plugin-widevinecdm