public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
Subject: Re: xorg-server-1.9.2-1 Fullscreen Issue
Date: Fri, 19 Nov 2010 13:37:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <SNT129-W66B341EE2B58251E6DD4DD4390@phx.gbl>

On 18/11/2010 12:33, Frederick Hansen wrote:
> Just FYI, after upgrading to xorg-server 1.9.2, any attempt to run in fullscreen results in an error.  Downgrading to version 1.8.2 seems to correct the issue.  Running either version in multiwindow also works.
> The contents of Xwin.log are shown below:
> Welcome to the XWin X Server
> Vendor: The Cygwin/X Project
> Release: (10902000)
> Build Date: 2010-11-03
> XWin was started with the following command line:
> /usr/bin/XWin -fullscreen -depth 8 -clipboard -silent-dup-error 
> [ 30091.406] (EE) XKB: Could not invoke xkbcomp
> [ 30091.406] (EE) XKB: Couldn't compile keymap
> [ 30091.406] XKB: Failed to compile keymap
> [ 30091.406] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
> [ 30091.406] 
> Fatal server error:
> [ 30091.406] Failed to activate core devices.


I can start X in fullscreen without problems using the same options.

Are you sure that removing -fullscreen allows the X server to start properly?
 This kind of failure (invoking xkbcomp) is usually caused by BLODA or rebase
problems preventing xkbcomp from being spawned.  It would be unusual for that
to only occur with certain options, but I guess it is possible.

Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

  reply	other threads:[~2010-11-19 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 12:33 Frederick Hansen
2010-11-19 13:37 ` Jon TURNEY [this message]
2011-01-21  4:38   ` Frederick D. Hansen
2011-01-24 17:48     ` Jon TURNEY
2011-01-26 13:24       ` Reinier Post

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:

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

  git send-email \ \ \ \ \

* 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).