This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: cygwin/xfree86 Unable to open X display after first success
- From: Christopher Faylor <cgf-cygwin-xfree at cygwin dot com>
- To: cygwin-xfree at cygwin dot com
- Cc: cygwin at cygwin dot com, sungtakdh at myrealbox dot com
- Date: Fri, 17 May 2002 17:52:17 -0400
- Subject: Re: cygwin/xfree86 Unable to open X display after first success
- References: <05e901c1fdeb$552710d0$0100a8c0@ATHLON>
- Reply-to: cygwin-xfree at cygwin dot com
Wrong mailing list. Redirected.
cgf
On Fri, May 17, 2002 at 05:39:30PM -0400, Dennis Hui wrote:
>Hi,
>
>I'm having problem with X display after first
>successful launch of an X application. (Prior to this
>I did xhost +) When I remote logged in to a remote
>host, I first exported the DISPLAY=<host-ip>:0.0 and
>started the X application (e.g. xclock, xeyes, or
>xterm). Then I quitted the application, and tried to
>run another X app., I got: ERROR: unable to open X
>display. I have trouble running any subsequent X
>display.
>
>I have to quit XFree86 and restart X Windows before I
>can start my X application again.
>
>When quitting XFree86, I get the following error
>message:
>$ xterm: fatal IO error 32 (Broken pipe) or
>KillClient on X server ":0.0"
>XIO: fatal IO error 113 (The connection was aborted)
>on X server ":0.0"xterm:
>fatal IO error 113 (The connection was aborted) or
>KillClient on X server ":0.0"
> after 3002 requests (3000 known processed) with
>3 events = remaining.
>
>The Cygwin/XFree86 base that I use is 4.2.0-1. Please
>let me know if I missed anything.
>Thanks,
>
>Attached is the output of cygcheck -s -v -r.
>
>Dennis Hui
--
Please do not send me personal email with cygwin questions.
Use the resources at http://cygwin.com/ .
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/