Had to upgrade as gmail claims the stable firefox is no longer supported. Options: 1. disable jit when USE=hardened 2. add enable paxctl p - did not check if it actually working. 3. anything else? Nov 03 11:52:24 [kernel] PAX: execution attempt in: <anonymous mapping>, 743505439000-743505449000 743505439000 Nov 03 11:52:24 [kernel] PAX: terminating task: /usr/lib64/firefox/firefox(firefox):4543, uid/euid: 1000/1000, PC: 000074350543ba58, SP: 00007b680758f008 Nov 03 11:52:24 [kernel] PAX: bytes at PC: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? Nov 03 11:52:24 [kernel] PAX: bytes at SP-8: 00007b680758f0c0 0000743508903654 0000000000000202 00007434e1478c00 0000000000000001 fffc7434eca47740 fff9000000000000 00007b680758f0c0 00007434e5eeb180 0000743507bf87a4 0000000000000701
Firefox-31.x , which is going stable very soon, already has paxctl -p. However, I had reports from others that said hardened was working fine with USE="jit" and -without- paxctl -p on firefox-32 and 33, which is why i removed it. Could I get you to try firefox-34.0_beta4 from mozilla-overlay with USE="jit" , and if that also fails then I'll re-add the paxctl -p. FYI, the preferable solution in general is to disable USE="jit" on hardened ; this is disabled by default on hardened profiles for this reason.
(In reply to Ian Stakenvicius from comment #1) > Firefox-31.x , which is going stable very soon, already has paxctl -p. > However, I had reports from others that said hardened was working fine with > USE="jit" and -without- paxctl -p on firefox-32 and 33, which is why i > removed it. ok, so it is not working :)) > Could I get you to try firefox-34.0_beta4 from mozilla-overlay with > USE="jit" , and if that also fails then I'll re-add the paxctl -p. oh... I will need time for this, first I will downgrade to 31... to avoid more issues... working browser is very important for me... :) > FYI, the preferable solution in general is to disable USE="jit" on hardened > ; this is disabled by default on hardened profiles for this reason. this is what I've done... but I do think that it is not enough to disable by default but either mask it or disable it unconditionally if hardened USE flag is provided.
If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team
