Red Hat Bugzilla – Bug 1468800
firefox causing multiple issues with selinux
Last modified: 2018-03-13 16:23:25 EDT
Created attachment 1295461 [details]
Description of problem: Firefox is causing multiple issues with selinux enforcing. It causes firefox to crash and also prevents firefox from printing to file.
Version-Release number of selected component (if applicable): firefox-52.2.0-1
How reproducible: Always
Steps to Reproduce:
1. Open firefox
2. On any website, click Ctrl + P to open print dialog
3. Select Print to file
4. Check if file is created at the said location
Firefox crashing :
Firefox crashes with "Gah. Your tab just crashed"
( Attaching backtrace )
Actual results: With Selinux enforcing, firefox is crashing and preventing printing to file
Expected results: Firefox should not crash or prevent printing to file
Following workaround makes firefox work as desired :
$ setsebool -P unconfined_mozilla_plugin_transition 0
However, this is unacceptable by customers as production environment is affected and they would not like to disable selinux on it. Also, multiple customers are affected.
It may be related to multiprocess. I think the customer has enabled e10s, which means that the web content is running in plugin-container which is blocked by SELinux. The plugin-container is also running NPAPI plugins (flash, java...) so that causes the SELinux confusion here.
A quick solution is to disable e10s by setting "browser.tabs.remote.force-disable" to true in about:config or create a .js pref file with this entry at /etc/firefox/pref directory.
See /usr/lib(64)/firefox/browser/defaults/preferences/firefox-redhat-default-prefs.js how the .js pref file looks like.
I checked my environment (RHEL7 + firefox-52.2.0-1.el7_3.x86_64) but could not see "browser.tabs.remote.force-disable".(Could not find it in FF45 either.) Is this pref exist in Firefox 45/52? Or did I miss anything?
Please advise. Thank you!
Ahh, I see. Then you need to add it, click by right mouse on any entry here and select "New" and "Boolean" and put the name there.
That comes from project Electrolysis which was introduced at Firefox 52, see https://wiki.mozilla.org/Electrolysis for details.