Chrome 52 not starting properly in RHEL 7

I'm trying to run Chrome 52 in a RHEL 7 server.

I'm running as a regular user:

> google-chrome 

Chrome itself starts, but the tabs are broken. Then I get the following errors:

[4003:4033:0728/115536:ERROR:zygote_communication_linux.cc(171)] Did not receive ping from zygote child [6:6:0728/115536:ERROR:zygote_linux.cc(634)] Zygote could not fork: process_type renderer numfds 5 child_pid -1 [4003:4033:0728/115536:ERROR:zygote_communication_linux.cc(171)] Did not receive ping from zygote child [6:6:0728/115536:ERROR:zygote_linux.cc(634)] Zygote could not fork: process_type renderer numfds 5 child_pid -1 [4003:4003:0728/115537:ERROR:child_process_launcher.cc(515)] Failed to launch child process [4003:4003:0728/115537:ERROR:child_process_launcher.cc(515)] Failed to launch child process 

I found out that running Chrome outside the sandbox mode makes it work:

> google-chrome --no-sandbox 

But then I get the following message:

[4131:4131:0728/120326:ERROR:browser_main_loop.cc(231)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.

It says that this is a deprecated feature and there are stability and security issues around this.

Is there any other way of making it work?

Replay

Category: linux Time: 2016-07-28 Views: 1

Related post

iOS development

Android development

Python development

JAVA development

Development language

PHP development

Ruby development

search

Front-end development

Database

development tools

Open Platform

Javascript development

.NET development

cloud computing

server

Copyright (C) avrocks.com, All Rights Reserved.

processed in 0.236 (s). 12 q(s)