all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 15392@debbugs.gnu.org
Subject: bug#15392: xorg-server FTBFS
Date: Mon, 16 Sep 2013 15:27:23 +0200	[thread overview]
Message-ID: <87k3iglww4.fsf@gnu.org> (raw)
In-Reply-To: <871u4pi625.fsf@tines.lan> (Mark H. Weaver's message of "Mon, 16 Sep 2013 03:22:58 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> xorg-server fails to build from source.  See below for the tail of the
> build log.  This is with aae4ead8142d4fd7c674a1e6e302f40469f878c6.

[...]

> PASS: input
> XKB: Failed to compile keymap
> Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
>
> Fatal server error:
> Failed to activate core devices.
>
> Please consult the The X.Org Foundation support
>          at http://wiki.x.org
>  for help.
>
> FAIL: xtest

This was discussed some time ago:

  http://lists.gnu.org/archive/html/bug-guix/2013-03/msg00140.html

It does seem like the xkeyboard-config data is not visible in its
default search path.

Apparently the X server can be started with
“-xkbdir /path/to/xkeyboard-config/etc/X11/xkb”, which should solve the
problem.

There were also discussions about introducing an ‘XKBPATH’ env. var.,
but I’m not sure if it was accepted upstream:
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324768>.

Thanks,
Ludo’.

  parent reply	other threads:[~2013-09-16 13:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16  7:22 bug#15392: xorg-server FTBFS Mark H Weaver
2013-09-16  7:38 ` Mark H Weaver
2013-09-16 13:27 ` Ludovic Courtès [this message]
2013-09-21 17:23   ` Andreas Enge
2013-09-21 20:02     ` Ludovic Courtès
2013-09-22  9:01       ` Andreas Enge
2013-09-22  9:09         ` Andreas Enge
2013-09-22 20:35         ` Ludovic Courtès
2013-09-23 17:22           ` Andreas Enge
2013-09-23 19:39             ` Ludovic Courtès
2013-09-25  7:00               ` Andreas Enge
2013-09-25 13:11                 ` Ludovic Courtès

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=87k3iglww4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=15392@debbugs.gnu.org \
    --cc=mhw@netris.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.