Workaround & Possible Cause - "Failed to activate core device - Could not invoke xkbcomp" on Failed X Server Launch
Tue Apr 17 10:51:00 GMT 2012
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.
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.
Volunteer Cygwin/X X Server maintainer
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin-xfree