After xinit, as soon as I strike the 'alt' key X is terminated due to stack smashing attack and the display and input is frozen until X is booted again. Reproducible: Always Steps to Reproduce: 1. Boot up Xorg 2. Strike ALT Actual Results: Display and input freeze, X process ends. Console output is: *** stack smashing detected ***: X - terminated X: stack smashing attack in function XkbHandleActions - terminated Report to http: bugs.gentoo.org xinit: connection to X server lost. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 203 requests (196 known processed) with 0 events remaining. Expected Results: The alt key should have functioned normally. I usually use it very often for whatever windowmanager I am using (evilwm or awesome). I apologise for replacing all slashes with spaces in the package atom and url; I'm afraid my slash key is broken and elinks does not make pasting easy. I have xorg-server-1.5.2 and xf86-input-keyboard-1.3.1 . I rebuilt both after gcc-config'ing to hardenednossp, but the problem remained.
Created attachment 169850 [details] emerge --info
This bug also occurs in xorg-server-1.4.2. I imagine every version of xorg-server that uses the new ABI (1.4+) is probably affected by this bug.
This is an old bug and is a problem with the old gcc 3.x ssp. I hit it a long time ago and the paxteam debugged it. gcc 4.2+ does not have this problem. Build xorg without the ssp.
I can concur that this problem still exists in 1.5.3-r5 on a hardened 2008.0 build. Rebuilding xorg-server with the i686-pc-linux-gnu-3.4.6-hardenednossp compiler fixed the issue and X now runs without a hitch. If this is historic and well known, why isn't it in the Xorg 1.5 upgrade documentation?
Created attachment 188496 [details] emerge --info
Fixed in portage via filtering SSP for <GCC4.