public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: Charles Sheridan <charles.e.sheridan@ericsson.com>
Subject: Re: Workaround & Possible Cause - "Failed to activate core device - Could not invoke xkbcomp" on Failed X Server Launch
Date: Tue, 17 Apr 2012 10:51:00 -0000 [thread overview]
Message-ID: <4F8D4B2A.6010208@dronecode.org.uk> (raw)
In-Reply-To: <17E00CAE050D8D4382EC2CA255A940514C3BF5C508@EUSAACMS0714.eamcs.ericsson.se>
On 13/04/2012 03:30, Charles Sheridan wrote:
> This week, after upgrading my Cygwin installation for the first time since ~April of 2011, X server startup failed, with the below oft-reported entries at the end of /cywin/var/log/xwin/Xwin.0.log --
>
> ...
> [ 10092.016] (II) GLX: Initialized Win32 native WGL GL provider for screen 0
> [ 10092.235] (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm
> [ 10092.235] (EE) XKB: Failed to load keymap. Loading default keymap instead.
> [ 10092.313] (EE) Couldn't open compiled keymap file /var/lib/xkb/server-0.xkm
> [ 10092.313] XKB: Failed to compile keymap
> [ 10092.313] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
> [ 10092.313]
> Fatal server error:
> [ 10092.313] Failed to activate core devices.
> [ 10092.313] Server terminated with error (1). Closing log file.
>
> This occurs on startup attempts from Xwin, startx, & startxwin.
>
> I have not previously seen X server startup failure, over 10 years of Cygwin-X use on several different mswin machines.
>
> X server startup failure persists after Cygwin re-installation following an HP Vista Enterprise laptop reboot, without any Cygwin processes running, and despite post-install run of several recommended variations on `rebaseall` -- `rebaseall -b 0x77000000` under both ash & dash, and without the -b arg.
>
> => WORKAROUND: The new "Xlaunch" in the All Programs/Cygwin-X dir off the Windows Start Button starts X without issue.
>
> => POSSIBLE CAUSE: The same Xwin.0.log errors are reported in several X windows fora for platforms other than Cygwin. The first link below is a long entry in a Debian forum concluding that the issue relates to a problematic memory module, that can be bypassed via the "nopat" option to XWin. I couldn't get the Cygwin XWin cmd to recognize this option.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646987
Read more carefully. "nopat" is a linux kernel option, which is being used
there to work-around a kernel bug.
So all that bug tells you is when running the xkbcomp program at xserver
startup fails, you get these error messages.
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2012-04-17 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 2:30 Charles Sheridan
2012-04-17 10:51 ` Jon TURNEY [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=4F8D4B2A.6010208@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=charles.e.sheridan@ericsson.com \
--cc=cygwin-xfree@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).