Just some followup. It appears to be a known issue. https://productforums.google.com/forum/#!msg/chrome/FJyJMTI2CAQ/u-5-M8QtAQAJ https://forums.opensuse.org/showthread.php/527688-Google-Chrome-not-working-... Launching chrome with a --no-sandbox option allows the browser to work. On 1020, Josef Fortier wrote:

A few days ago chrome quit working on my Leap 42.3 desktop.

Starting from a command line shows references to "zygote" fork issues.

Most google results seem to be from a while ago.

It occurs on a re-install, on all three version from the suse repository and on the official google chrome rpm.

This is the output (I'd assume the root cert error is harmless)

[1326:1363:1020/121628.684837:ERROR:nss_util.cc(725)] After loading Root Certs, loaded==false: NSS error code: -8018 ATTENTION: default value of option force_s3tc_enable overridden by environment. [1326:1361:1020/121628.792864:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child [5:5:1020/121628.792981:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1 .... (more repetitions of the last two lines)

Thanks for any help :-)

-- __________________________________________________________________________ Josef Fortier Systems Administrator fortier@augsburg.edu Phone: 612-330-1479 __________________________________________________________________________ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org