Description of problem: $ chrome [5765:5765:0312/224732:ERROR:child_process_launcher.cc(443)] Failed to launch child process [5765:5781:0312/224732:ERROR:zygote_host_impl_linux.cc(385)] Did not receive ping from zygote child [5767:5767:0312/224732:ERROR:zygote_linux.cc(629)] Zygote could not fork: process_type renderer numfds 5 child_pid -1 [5765:5781:0312/224732:ERROR:zygote_host_impl_linux.cc(385)] Did not receive ping from zygote child [5767:5767:0312/224732:ERROR:zygote_linux.cc(629)] Zygote could not fork: process_type renderer numfds 5 child_pid -1 [5765:5765:0312/224732:ERROR:child_process_launcher.cc(443)] Failed to launch child process [5765:5765:0312/224732:ERROR:child_process_launcher.cc(443)] Failed to launch child process [5765:5781:0312/224732:ERROR:zygote_host_impl_linux.cc(385)] Did not receive ping from zygote child [5767:5767:0312/224732:ERROR:zygote_linux.cc(629)] Zygote could not fork: process_type renderer numfds 5 child_pid -1 [5765:5781:0312/224732:ERROR:zygote_host_impl_linux.cc(385)] Did not receive ping from zygote child [5767:5767:0312/224732:ERROR:zygote_linux.cc(629)] Zygote could not fork: process_type renderer numfds 5 child_pid -1 [5765:5765:0312/224732:ERROR:child_process_launcher.cc(443)] Failed to launch child process [5765:5765:0312/224732:ERROR:child_process_launcher.cc(443)] Failed to launch child process [5765:5781:0312/224732:ERROR:zygote_host_impl_linux.cc(385)] Did not receive ping from zygote child [5767:5767:0312/224732:ERROR:zygote_linux.cc(629)] Zygote could not fork: process_type renderer numfds 5 child_pid -1 [5765:5781:0312/224732:ERROR:zygote_host_impl_linux.cc(385)] Did not receive ping from zygote child [5767:5767:0312/224732:ERROR:zygote_linux.cc(629)] Zygote could not fork: process_type renderer numfds 5 child_pid -1 Version-Release number of selected component (if applicable): selinux-policy-targeted-3.13.1-178.fc24.noarch How reproducible: always Steps to Reproduce: 1. Install Google Chrome from https://www.google.com/chrome/browser/desktop/ 2. Run it 3. Actual results: failure to work properly - pages cannot be opened Additional info: This policy resolves this issue: #============= chrome_sandbox_t ============== #!!!! This avc is allowed in the current policy allow chrome_sandbox_t self:process setcap;
This has been long fixed.