public inbox for
help / color / mirror / Atom feed
From: "David M. Karr" <>
Subject: Re: Tried to fix  "Doing vfork: resource temporarily unavailable" error with Emacs, now can't start X server
Date: Thu, 21 Apr 2011 01:02:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 4/18/2011 5:12 AM, Ken Brown wrote:
> On 4/17/2011 6:30 PM, David M. Karr wrote:
>> Cygwin 1.7.8 (and 1.7.9), Win7SP1.
>> I was having issues with my Emacs startup occasionally failing with
>> "Doing vfork: resource temporarily unavailable".  I found a link that
>> alleged to have the solution to this
>> (
> The advice about libncurses on that page is obsolete.  It applied to 
> old versions of emacs.  The suggestion of running rebaseall is good 
> but...
>> I followed these steps, although when I looked at "libncurses7", I saw
>> it was set to "Skip", and that I had versions 8, 9, and 10.  So, I set
>> those to reinstall and continued the update.  It also updated some other
>> things, including updating me from Cygwin 1.7.8 to 1.7.9.
> you should try rebaseall now.
I tried to reply to this a while ago, but it never showed up on the list.

This didn't fix the problem.  I still can't start the X server.  It 
fails with "Failed to activate core devices".

Here is the log output:

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601]
Package version 1.10.0-1 built 2011-03-15

XWin was started with the following command line:

X :0 -multiwindow

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1920 h 1080
winInitializeDefaultScreens - native DPI x 96 y 96
[181003.592] (II) xorg.conf is not supported
[181003.592] (II) See for 
more information
[181003.592] LoadPreferences: /home/David/.XWinrc not found
[181003.592] LoadPreferences: Loading /etc/X11/system.XWinrc
[181003.592] LoadPreferences: Done parsing the configuration file...
[181003.654] winDetectSupportedEngines - DirectDraw installed, allowing 
[181003.654] winDetectSupportedEngines - Windows NT, allowing PrimaryDD
[181003.654] winDetectSupportedEngines - DirectDraw4 installed, allowing 
[181003.763] winDetectSupportedEngines - Returning, supported engines 
[181003.763] winSetEngine - Multi Window or Rootless => ShadowGDI
[181003.763] winScreenInit - Using Windows display depth of 32 bits per 
[181003.779] winAllocateFBShadowGDI - Creating DIB with width: 1920 
height: 1080 depth: 32
[181003.779] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[181003.779] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 
BPRGB 8 d 24 bpp 32
[181003.779] winInitMultiWindowWM - Calling pthread_mutex_lock ()
[181003.779] winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
[181003.779] Screen 0 added at virtual desktop coordinate (0,0).
[181003.779] MIT-SHM extension disabled due to lack of kernel support
[181003.794] XFree86-Bigfont extension local-client optimization 
disabled due to lack of shared memory support in the kernel
[181003.826] (II) AIGLX: Loaded and initialized /usr/lib/dri/
[181003.826] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[181003.841] [dix] Could not init font path element 
/usr/share/fonts/OTF/, removing from list!
[181003.841] [dix] Could not init font path element 
/usr/share/fonts/Type1/, removing from list!
[181003.966] (EE) XKB: Could not invoke xkbcomp
[181003.966] (EE) XKB: Couldn't compile keymap
[181003.966] (EE) XKB: Failed to load keymap. Loading default keymap 
[181004.091] (EE) XKB: Could not invoke xkbcomp
[181004.091] (EE) XKB: Couldn't compile keymap
[181004.091] XKB: Failed to compile keymap
[181004.091] Keyboard initialization failed. This could be a missing or 
incorrect setup of xkeyboard-config.
Fatal server error:
[181004.091] Failed to activate core devices.

Unsubscribe info:
Problem reports:

      reply	other threads:[~2011-04-21  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-17 22:30 David M. Karr
2011-04-18 12:13 ` Ken Brown
2011-04-21  1:02   ` David M. Karr [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:

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