public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Still can't run XServer or any apps that require it
Date: Mon, 25 Apr 2011 17:07:00 -0000 [thread overview]
Message-ID: <20110425170715.GB3841@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4DB5920C.9010202@dronecode.org.uk>
On Mon, Apr 25, 2011 at 04:23:56PM +0100, Jon TURNEY wrote:
>On 23/04/2011 17:47, David M. Karr wrote:
>> Almost a week ago now, I've been unable to run my XServer, and thus any of the
>> apps that normally run with it, like Emacs.
>
>I realise this situation is an inconvenience, but please don't post to
>multiple lists just because you don't get a quick response.
>
>> When I run "startxwin", it just
>> says "failed to activate core devices".
>[snip]
>> [498341.949] (EE) XKB: Could not invoke xkbcomp
>> [498341.949] (EE) XKB: Couldn't compile keymap
>> [498341.949] (EE) XKB: Failed to load keymap. Loading default keymap instead.
>> [498342.089] (EE) XKB: Could not invoke xkbcomp
>> [498342.089] (EE) XKB: Couldn't compile keymap
>> [498342.089] XKB: Failed to compile keymap
>> [498342.089] Keyboard initialization failed. This could be a missing or
>> incorrect setup of xkeyboard-config.
>> [498342.089] Fatal server error: Failed to activate core devices.
>> ------------------------------
>>
>> I looked in the FAQ for the entry corresponding to this error, but none of the
>> steps found any issues. I've tried doing "rebaseall" according to the
>> instructions, but that hasn't made any difference. In fact, my problems
>> started when I ran "rebaseall" to fix a different problem. I was getting
>> "Doing vfork: resource temporarily unavailable" when I started up Emacs, and
>> some advice I found suggested running "rebaseall".
>
>Unfortunately, rebaseall is a rather limited workaround, rather than a
>solution for these issues (for reasons which have been discussed extensively
>in the past)
>
>There has been a recent cygwin DLL change which *might* help in this
>situation, so I'd suggest you try the 2011-04-07 snapshot from [1] and see if
>that makes a difference. (I wouldn't recommend later ones as they seem to have
>a regression in a different area)
>
>[1] http://cygwin.com/snapshots/
Also, I've found that using a different base address with rebaseall
seems to help with some X problems:
dash -c "rebaseall -b 0x77000000"
http://cygwin.com/ml/cygwin/2011-04/msg00306.html
cgf
--
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/
next prev parent reply other threads:[~2011-04-25 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 16:47 David M. Karr
2011-04-25 15:23 ` Jon TURNEY
2011-04-25 17:07 ` Christopher Faylor [this message]
2011-04-26 5:16 ` David M. Karr
2011-04-26 15:37 ` Larry Hall (Cygwin-X)
2011-04-28 13:25 ` Jon TURNEY
2011-05-07 11:51 ` Ryan Johnson
2011-04-26 1:32 ` David M. Karr
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=20110425170715.GB3841@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).