From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18619 invoked by alias); 17 Apr 2012 10:51:34 -0000 Received: (qmail 18603 invoked by uid 22791); 17 Apr 2012 10:51:33 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SARE_SUB_OBFU_OTHER,TW_KB,TW_XK X-Spam-Check-By: sourceware.org Received: from mercury.karoo.kcom.com (HELO smtpout.karoo.kcom.com) (212.50.160.61) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 17 Apr 2012 10:51:18 +0000 Received: from 213-152-38-55.dsl.eclipse.net.uk (HELO [192.168.1.111]) ([213.152.38.55]) by smtpout.karoo.kcom.com with ESMTP; 17 Apr 2012 11:51:18 +0100 Message-ID: <4F8D4B2A.6010208@dronecode.org.uk> Date: Tue, 17 Apr 2012 10:51:00 -0000 From: Jon TURNEY Reply-To: cygwin-xfree User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: Charles Sheridan Subject: Re: Workaround & Possible Cause - "Failed to activate core device - Could not invoke xkbcomp" on Failed X Server Launch References: <17E00CAE050D8D4382EC2CA255A940514C3BF5C508@EUSAACMS0714.eamcs.ericsson.se> In-Reply-To: <17E00CAE050D8D4382EC2CA255A940514C3BF5C508@EUSAACMS0714.eamcs.ericsson.se> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2012-04/txt/msg00056.txt.bz2 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/