Due to SELinux preventing /opt/google/chrome-beta/chrome from using the setcap access on a process, the Google Chrome process previously terminated unexpectedly and the sandbox initialization failed. This update adds the chrome_sandbox_t SELinux policy, and Google Chrome no longer crashes in the described scenario.
This bug has been copied from bug #1251996 and has been proposed
to be backported to 7.1 z-stream (EUS).
Author: Lukas Vrabec <firstname.lastname@example.org>
Date: Tue Aug 18 09:57:50 2015 +0200
Allow chrome setcap to itself.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.