public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: rp@win.tue.nl (Reinier Post) To: cygwin-xfree@cygwin.com Subject: Re: xorg-server-1.9.2-1 Fullscreen Issue Date: Wed, 26 Jan 2011 13:24:00 -0000 [thread overview] Message-ID: <20110126132447.GA21873@win.tue.nl> (raw) In-Reply-To: <4D3DBB7C.1060608@dronecode.org.uk> On Mon, Jan 24, 2011 at 05:48:44PM +0000, Jon TURNEY wrote: > On 21/01/2011 04:38, Frederick D. Hansen wrote: > > On Fri, 2010-11-19 at 13:37 +0000, Jon TURNEY wrote: > >> 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: 1.9.2.0 (10902000) > >>> Build Date: 2010-11-03 > >>> > >>> XWin was started with the following command line: > >>> > >>> /usr/bin/XWin -fullscreen -depth 8 -clipboard -silent-dup-error By the way, on my machine, this is just: X :0 -multiwindow > >> [snip] > >>> [ 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. This was the same for me. > >> Are you sure that removing -fullscreen allows the X server to start properly? I didn't have it in the first place. > I use XP SP3. I can't reproduce this problem. > > The problem going away when you remove (and hence prevent from loading) the > dynamically loaded swrast_dri.so *really* makes this look like a remap problem. I'm on Windows 7. Renaming /usr/lib/dri/swrast_dri.so fixed the problem for me. I then renamed it back and ran rebase on it with the defaults used in rebaseall. X is still starting up. I then created rebase.lst using the commands used in rebaseall. /usr/lib/dri/swrast_dri.so is in there. But I have run rebaseall immediately prior to starting X and it was still failing to start. So it does appear to be a rebase problem, and I have no clue why rebaseall couldn't fix it. (It was completing successfully.) > There is some work upstream to remove this rather pointless fork/exec of > xkbcomp and replace it with libxkbcommon, but that now seems unlikely to > appear in X server 1.10. > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer -- Reinier Post -- 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:[~2011-01-26 13:24 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 2011-01-21 4:38 ` Frederick D. Hansen 2011-01-24 17:48 ` Jon TURNEY 2011-01-26 13:24 ` Reinier Post [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=20110126132447.GA21873@win.tue.nl \ --to=rp@win.tue.nl \ --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: linkBe 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).