Bug 1317171 - The official Google Chrome does not work under Fedora 24
The official Google Chrome does not work under Fedora 24
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
24
All Linux
unspecified Severity urgent
: ---
: ---
Assigned To: Miroslav Grepl
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-12 13:06 EST by Artem S. Tashkinov
Modified: 2017-07-24 17:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-24 17:31:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Artem S. Tashkinov 2016-03-12 13:06:50 EST
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;
Comment 1 Artem S. Tashkinov 2017-07-24 17:31:35 EDT
This has been long fixed.

Note You need to log in before you can comment on or make changes to this bug.