Tried to fix "Doing vfork: resource temporarily unavailable" error with Emacs, now can't start X server

2011-04-17 Thread David M. Karr

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 
(http://blog.cottee.org/2008/05/cygwin-emacs-problems.html).


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.


Now, when I run "startxwin", it chugs for a bit and then presents an 
error dialog saying "Failed to activate core devices".  The log file 
contents follows this.  It fails like this every time now.

---
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.10.0.0
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
[46.020] (II) xorg.conf is not supported
[46.020] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for 
more information

[46.020] LoadPreferences: /home/David/.XWinrc not found
[46.020] LoadPreferences: Loading /etc/X11/system.XWinrc
[46.020] LoadPreferences: Done parsing the configuration file...
[50.419] winDetectSupportedEngines - DirectDraw installed, allowing 
ShadowDD

[50.419] winDetectSupportedEngines - Windows NT, allowing PrimaryDD
[50.419] winDetectSupportedEngines - DirectDraw4 installed, allowing 
ShadowDDNL
[50.466] winDetectSupportedEngines - Returning, supported engines 
001f

[50.466] winSetEngine - Multi Window or Rootless => ShadowGDI
[50.466] winScreenInit - Using Windows display depth of 32 bits per 
pixel
[50.466] winAllocateFBShadowGDI - Creating DIB with width: 1920 
height: 1080 depth: 32

[50.466] winFinishScreenInitFB - Masks: 00ff ff00 00ff
[50.466] winInitVisualsShadowGDI - Masks 00ff ff00 00ff 
BPRGB 8 d 24 bpp 32

[50.466] winInitMultiWindowWM - Calling pthread_mutex_lock ()
[50.466] winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
[50.466] Screen 0 added at virtual desktop coordinate (0,0).
[52.541] MIT-SHM extension disabled due to lack of kernel support
[52.541] XFree86-Bigfont extension local-client optimization 
disabled due to lack of shared memory support in the kernel

[53.102] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
[53.102] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[53.165] [dix] Could not init font path element 
/usr/share/fonts/OTF/, removing from list!
[53.165] [dix] Could not init font path element 
/usr/share/fonts/Type1/, removing from list!

[53.523] (EE) XKB: Could not invoke xkbcomp
[53.523] (EE) XKB: Couldn't compile keymap
[53.523] (EE) XKB: Failed to load keymap. Loading default keymap 
instead.

[53.633] (EE) XKB: Could not invoke xkbcomp
[53.633] (EE) XKB: Couldn't compile keymap
[53.633] XKB: Failed to compile keymap
[53.633] Keyboard initialization failed. This could be a missing or 
incorrect setup of xkeyboard-config.

[53.633]
Fatal server error:
[53.633] Failed to activate core devices.


--
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/



Re: Tried to fix "Doing vfork: resource temporarily unavailable" error with Emacs, now can't start X server

2011-04-20 Thread David M. Karr

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
(http://blog.cottee.org/2008/05/cygwin-emacs-problems.html).


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
Release: 1.10.0.0
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 http://x.cygwin.com/docs/faq/cygwin-x-faq.html 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 
ShadowDD

[181003.654] winDetectSupportedEngines - Windows NT, allowing PrimaryDD
[181003.654] winDetectSupportedEngines - DirectDraw4 installed, allowing 
ShadowDDNL
[181003.763] winDetectSupportedEngines - Returning, supported engines 
001f

[181003.763] winSetEngine - Multi Window or Rootless => ShadowGDI
[181003.763] winScreenInit - Using Windows display depth of 32 bits per 
pixel
[181003.779] winAllocateFBShadowGDI - Creating DIB with width: 1920 
height: 1080 depth: 32

[181003.779] winFinishScreenInitFB - Masks: 00ff ff00 00ff
[181003.779] winInitVisualsShadowGDI - Masks 00ff ff00 00ff 
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/swrast_dri.so
[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 
instead.

[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.

[181004.091]
Fatal server error:
[181004.091] Failed to activate core devices.


--
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/



Still can't run XServer or any apps that require it

2011-04-23 Thread David M. Karr

Cygwin 1.7.9 on Win7SP1.

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.  When I run 
"startxwin", it just says "failed to activate core devices".


Here's the XWin.0.log:

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.10.1.0
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win32)
Package: version 1.10.1-1 built 2011-04-22

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
[498341.590] (II) xorg.conf is not supported
[498341.590] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for 
more information

[498341.590] LoadPreferences: /home/David/.XWinrc not found
[498341.590] LoadPreferences: Loading /etc/X11/system.XWinrc
[498341.605] LoadPreferences: Done parsing the configuration file...
[498341.652] winDetectSupportedEngines - DirectDraw installed, allowing 
ShadowDD

[498341.652] winDetectSupportedEngines - Windows NT, allowing PrimaryDD
[498341.652] winDetectSupportedEngines - DirectDraw4 installed, allowing 
ShadowDDNL
[498341.730] winDetectSupportedEngines - Returning, supported engines 
001f

[498341.730] winSetEngine - Multi Window or Rootless => ShadowGDI
[498341.730] winScreenInit - Using Windows display depth of 32 bits per 
pixel
[498341.746] winAllocateFBShadowGDI - Creating DIB with width: 1920 
height: 1080 depth: 32

[498341.746] winFinishScreenInitFB - Masks: 00ff ff00 00ff
[498341.746] winInitVisualsShadowGDI - Masks 00ff ff00 00ff 
BPRGB 8 d 24 bpp 32

[498341.746] winInitMultiWindowWM - Calling pthread_mutex_lock ()
[498341.761] Screen 0 added at virtual desktop coordinate (0,0).
[498341.761] winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
[498341.761] MIT-SHM extension disabled due to lack of kernel support
[498341.761] XFree86-Bigfont extension local-client optimization 
disabled due to lack of shared memory support in the kernel

[498341.808] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
[498341.808] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[498341.808] [dix] Could not init font path element 
/usr/share/fonts/OTF/, removing from list!
[498341.808] [dix] Could not init font path element 
/usr/share/fonts/Type1/, removing from list!

[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:
[498342.089] 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".


I've run "cygcheck -c" and got all OK.  I ran "cygcheck -s" and the only 
part that seemed vaguely suspicious was this excerpt:


   12k 2010/08/03 C:\/usr/bin/cygrunsrv: warning: OpenService failed 
for 'DcomLaunch': Win32 error 5

Access is denied.
/usr/bin/cygrunsrv: warning: OpenService failed for 'pla': Win32 error 5
Access is denied.
/usr/bin/cygrunsrv: warning: OpenService failed for 'QWAVE': Win32 error 5
Access is denied.
/usr/bin/cygrunsrv: warning: OpenService failed for 'RpcEptMapper': 
Win32 error 5

Access is denied.
/usr/bin/cygrunsrv: warning: OpenService failed for 'RpcSs': Win32 error 5
Access is denied.
cygwin\bin\cygXcomposite-1.dll


--
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/



Re: Still can't run XServer or any apps that require it

2011-04-25 Thread David M. Karr

On 4/25/2011 8:23 AM, 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.


I didn't do that entirely because I hadn't seen a response.  I 
considered the possibility that this was caused by an issue outside of 
the X server itself.



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/


Thanks, I'll move towards that.

--
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/



Re: Still can't run XServer or any apps that require it

2011-04-25 Thread David M. Karr

On 4/25/2011 10:07 AM, Christopher Faylor wrote:

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 0x7700"

http://cygwin.com/ml/cygwin/2011-04/msg00306.html



Ok, that appears to have fixed my problem.  Is that a "permanent" fix?

--
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/