Google Chrome not launching CentOS 7

Amarnath Prabhakar November 28, 2016 0

[8545:8545:1128/152253:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I’m aborting now. You need to make sure that /opt/google/chrome/chrome-sandbox is owned by root and has mode 4755.
Aborted (core dumped)

Recently I had installed CentOS 7 on a old laptop and had it working.

Since, I was new to the linux aspects of things it was tough to manage and operate CentOS and was making many mistakes in the process. One of the mistake that I had done was to change root privileges from the root user to the system user. This crashed my OS and was locked out of CentOS. After many many hours of troubleshooting eventually get access to the root and user logins. I would make another post about the reversal with the steps involved.

This post however is about how this crazy hindsight crashed Google Chrome and the process of retrieving the same.

The beginning of this post has the error that was thrown when I tried to initiate google-chrome from the terminal in CentOS. This trial was because the Chrome Icon on the desktop would not initiate chrome.

After some amount of research I realized that although the sandbox folder for Google Chrome was owned by the root user the permissions were 0777. This folder required a 4755 permission to initiate the Chrome browser. A simple code as below solved the problem

sudo chmod 4755 /opt/google/chrome/chrome-sandbox

chmod change

 

Once this was done, Google Chrome was back to it’s glorious self.

Leave A Response »