I though this got fixed a few weeks back. I did a fresh install (not upgrade) of the latest tree, and tried starting firefox, and got the attached dialog. here's what ended up in dmesg.. audit(1139975061.034:105): avc: denied { execstack } for pid=3276 comm="firefox-bin" scontext=user_u:system_r:unconfined_t:s0 tcontext=user_u:system_r:unconfined_t:s0 tclass=process Firefox then starts up, but SSL browsing is impossible.
Created attachment 124664 [details] firefox dialog on startup
The question is why does firefox need execstack to do SSL Browsing? Is this really necessary or is this a problem in the library? We can mask the problem by allowing firefox execstack, but is that what we want?
*** This bug has been marked as a duplicate of 180726 ***