1383141 - Electrolysis enablement and inter-process communication causing SELinux errors

Status: RESOLVED DUPLICATE of bug 1376559

(Core :: IPC, defect)

Description

[R P Herrold]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170614180111

Steps to reproduce:

see https://bugzilla.redhat.com/show_bug.cgi?id=1473754 

for the long form discussion --- basically running Firefox in a non-privileged userid through a SSH X-forwarding tunnel on localhost


Actual results:

IPC failures due to SELinux lock up the browser

I attach the needed SELinux 'fix' -- an additional rule to enable IPC in the Red Hat bug filing


Expected results:

no lockups, and working IPC

I am running with disabled 

browser.tabs.remote.autostart = false
browser.tabs.remote.autostart.2 = false

presently, to try to remove most of Electrolysis from the issue

Comment 1

[R P Herrold]

I _was_ running with all the autostart set to false, but some unknown process invisibly re-enabled 
   browser.tabs.remote.autostart.2

without asking

I would like to be able to persistently 'opt out' of being a test guinea pig.

How can I 'lock' this setting against change, or at a minimum 'grep' a log daily to see when it is (silently) tampered with?

-- Russ herrold

Comment 2

[Jed Davis [:jld] (on leave until 08-31)]

This is a duplicate of bug 1376559.

And, for what it's worth, browser.tabs.remote.autostart.2 is the last of the e10s prefs.  (I remember when those started being added on Nightly and I had to keep turning them off because I used add-ons that weren't ported to e10s yet and, yes, it was annoying.)

Comment 3

[R P Herrold]

thank you Jed Davis