Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The latest chromium-browser releases fail to start when home directories are on NFS. It seems an updated SELinux policy is needed to allow chrome_sandbox_t access to nfs_t (and autofs_t) when the use_nfs_home_dirs SELinux boolean is set.
Version-Release number of selected component (if applicable):
chromium-browser-39.0.2171.99-1.el6_6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Start chromium-browser as a user with an NFS mounted home directory
2.
3.
Actual results:
The following error is thrown and no windows is opened.
$ chromium-browser
[0122/113309:ERROR:nss_util.cc(94)] Failed to create /users/system/rtheys/.pki/nssdb directory.
[0122/113309:FATAL:chrome_main_delegate.cc(359)] Check failed: process_type.empty(). Unable to get the user data directory for process type: zygote
Expected results:
Chromium opens.
Additional info:
The following SELinux module fixes this for me:
module esat_chromium 1.0;
require {
type autofs_t;
type chrome_sandbox_t;
type nfs_t;
class dir { getattr search };
class filesystem getattr;
}
#============= chrome_sandbox_t ==============
allow chrome_sandbox_t autofs_t:dir { getattr search };
allow chrome_sandbox_t nfs_t:filesystem getattr;
Description of problem: The latest chromium-browser releases fail to start when home directories are on NFS. It seems an updated SELinux policy is needed to allow chrome_sandbox_t access to nfs_t (and autofs_t) when the use_nfs_home_dirs SELinux boolean is set. Version-Release number of selected component (if applicable): chromium-browser-39.0.2171.99-1.el6_6.x86_64 How reproducible: Always Steps to Reproduce: 1. Start chromium-browser as a user with an NFS mounted home directory 2. 3. Actual results: The following error is thrown and no windows is opened. $ chromium-browser [0122/113309:ERROR:nss_util.cc(94)] Failed to create /users/system/rtheys/.pki/nssdb directory. [0122/113309:FATAL:chrome_main_delegate.cc(359)] Check failed: process_type.empty(). Unable to get the user data directory for process type: zygote Expected results: Chromium opens. Additional info: The following SELinux module fixes this for me: module esat_chromium 1.0; require { type autofs_t; type chrome_sandbox_t; type nfs_t; class dir { getattr search }; class filesystem getattr; } #============= chrome_sandbox_t ============== allow chrome_sandbox_t autofs_t:dir { getattr search }; allow chrome_sandbox_t nfs_t:filesystem getattr;