public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: mino@aon.at
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Xorg fails to fork therefore cannot invoke xkbcomp
Date: Wed, 3 Jun 2009 22:15:59 +0200	[thread overview]
Message-ID: <20090603201559.GB21553@thanatos.hades.local> (raw)
In-Reply-To: <72183297a6e7d7e4c03dbac1cf2217f8.squirrel@atoth.sote.hu>

> Xorg.log
> (**) Option "xkb_rules" "evdev"
> (**) Option "xkb_model" "evdev"
> (**) Option "xkb_layout" "hu,us"
> (**) Option "xkb_variant" "standard"
> (**) Option "xkb_options" "grp:shift_toggle,compose:ralt"
> (EE) XKB: Could not invoke xkbcomp
> (EE) XKB: Couldn't compile keymap
> (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap
> 
> grsec.log
> grsec: (root:U:/usr/bin/Xorg) failed fork with errno -12 by
> /usr/bin/Xorg[X:pid] uid/euid:0/0 gid/egid:0/0, parent
> /usr/sbin/gdm-binary[gdm:pid] uid/euid:0/0 gid/egid:0/0
> 
> Result: wrong keyboard layout, compose key don't work, I cannot even
> switch to a terminal.
> 
> Any clues how to solve it?
> 
> Regards:
> Dw.
> -- 
> dr Tóth Attila, Radiológus, 06-20-825-8057, 06-30-5962-962
> Attila Toth MD, Radiologist, +36-20-825-8057, +36-30-5962-962
> 
> 

I think I experienced a similar problem some time ago.
Changing the pax flags on /usr/bin/Xorg worked for me.

Pax somehow prevented Xorg from compiling a new keymap.

Type "paxctl -pemrxs /usr/bin/Xorg", which should disable all
restrictions and try it again.

If I recall correctly, I could reset the flags to their default values
(paxctl -zxe /usr/bin/Xorg) after Xorg started with the correct keymap.

I hope this helps.

Regards,

Mino



      reply	other threads:[~2009-06-03 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 13:50 [gentoo-hardened] Xorg fails to fork therefore cannot invoke xkbcomp atoth
2009-06-03 20:15 ` mino [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090603201559.GB21553@thanatos.hades.local \
    --to=mino@aon.at \
    --cc=gentoo-hardened@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox