This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: "no buffer space available" on Win2K
- From: Vince Hoffman <Vince dot Hoffman at uk dot circle dot com>
- To: "'cygwin-xfree at cygwin dot com'" <cygwin-xfree at cygwin dot com>
- Date: Fri, 2 May 2003 14:28:55 +0100
- Subject: RE: "no buffer space available" on Win2K
- Reply-to: cygwin-xfree at cygwin dot com
If its of any interest i can now definatley duplicate my problem on my box
without involving X at all. (It does seem to involve cygwin but i'm hoping i
can verify that and get something more concrete before i start bugging any
lists again.)
Vince
> -----Original Message-----
> From: Karl Waclawek [mailto:karl@waclawek.net]
> Sent: 02 May 2003 14:14
> To: cygwin-xfree@cygwin.com
> Subject: Re: "no buffer space available" on Win2K
>
>
> Harold,
>
> as promised I tried again with eval 'ssh-agent' commented out.
> It seemed to go well for about 5 minutes of heavy windowing
> interaction with two copies of Kylix, and I was ready to call
> it a success, when suddenly the X screen disappeared, then re-appeared
> with the grey surface (as it did before).
>
> One slight difference: Only some apps would now give me the
> "no buffer space available" error. startxwin.sh, for instance,
> would simply report: "cannot connect to 127.0.0.1".
> Again, the only remedy was to re-boot the OS.
>
> Karl
>