Fails to boot to GDM login screen with the following error 2.477058] PAX: execution attempt in: <anonymous mapping>, 2f668ca8000-2f668cb9000 2f668ca8000 [ 2.477062] PAX: terminating task: /usr/bin/gnome-shell(gnome-shell):403, uid/euid: 105/105, PC: 000002f668ca9760, SP: 000003ae4bcf5618 [ 2.477064] PAX: bytes at PC: 55 48 89 e5 53 41 54 41 55 41 56 41 57 ff 75 18 49 89 e6 49 [ 2.477073] PAX: bytes at SP-8: 000003ae4bcf5700 000002f66160600e 00000000614e2be4 000003ae4bcf5758 000002f668ca9760 0000ffff00000001 0000006d99855880 0000000000000000 0000006d997ef800 0000006d9984c8e0 0000006d998f0bb0 Disabling mprotect in default gnome-shell PaX flags resovles this problem.
Created attachment 375492 [details] Emerge --info
Isn't that handled in src_install already ? > elif has_version '>=dev-lang/spidermonkey-1.8.7[jit]'; then > pax-mark m "${ED}usr/bin/gnome-shell" > fi
(In reply to Gilles Dartiguelongue from comment #2) > Isn't that handled in src_install already ? > > > elif has_version '>=dev-lang/spidermonkey-1.8.7[jit]'; then > > pax-mark m "${ED}usr/bin/gnome-shell" > > fi Spidermonkey is built without "jit" in my case dev-lang/spidermonkey-24.2.0-r1:24 USE="icu system-icu -debug -jit -minimal -static-libs {-test}"
I guess it would be a little difficult but could you check if this is a new behavior compared to 3.10 ?
(In reply to Gilles Dartiguelongue from comment #4) > I guess it would be a little difficult but could you check if this is a new > behavior compared to 3.10 ? No problem i cloned my ssd to another before adding the gnome-3.12 overlay. I updated the "clone" gnome 3.10 system via portage for non-overlay stuff to be close as possible to "current" system. Obviously no slotted spidermonkey-24, but the same default hardened profile flags ie "-jit" Gnome-3.10 performed as expected with no need to change default PAX flags.
My mistake Spidermonkey-24 is slotted with version 17, but still the same conclusions with Gnome-3.10 and it's gnome-shell defaults pax flags.
Not sure if the problem would be in spidermonkey or gnome-shell really :(
if gnome-shell requires spidermonkey:17[jit] , then the problem may very well be in spidermonkey. However, as per evidenced above I expect gnome-shell has been built against spidermonkey:17[-jit] and so it wouldn't be spidermonkey's problem.
(In reply to Ian Stakenvicius from comment #8) > if gnome-shell requires spidermonkey:17[jit] , then the problem may very > well be in spidermonkey. However, as per evidenced above I expect > gnome-shell has been built against spidermonkey:17[-jit] and so it wouldn't > be spidermonkey's problem. Ok just to follow up here: gnome-shell-3.12 requires gjs-1.39 and above. Currently in the tree, the only package satisfying this is gjs-1.40, which requires spidermonkey:24. Until very recently, the 'jit' use flag was not properly disabling all jit-related code (upstream added or renamed the jit engines, essentially) -- see bug 510982. Could someone confirm that this bug is still present with spidermonkey-24.2.0-r2[-jit] installed?
(In reply to Ian Stakenvicius from comment #9) > gnome-shell-3.12 requires gjs-1.39 and above. Currently in the tree, the > only package satisfying this is gjs-1.40, which requires spidermonkey:24. > Until very recently, the 'jit' use flag was not properly disabling all > jit-related code (upstream added or renamed the jit engines, essentially) -- > see bug 510982. > > Could someone confirm that this bug is still present with > spidermonkey-24.2.0-r2[-jit] installed? This appears to have solved the problem for me . I reinstalled gnome-shell and it worked with it's default PaX flags. Many thanks Ian.
Excellent! *** This bug has been marked as a duplicate of bug 510982 ***
