public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jack Ostroff <ostroffjh@sbcglobal.net>
To: cygwin-xfree@cygwin.com
Subject: odd case of "Can't connect to display"
Date: Thu, 09 Sep 2010 23:45:00 -0000 [thread overview]
Message-ID: <1284075889.11622.1@ffortso4> (raw)
I'm doing "ssh user@host -X" to get to my linux desktop machine from my
laptop running Cygwin under Windows Vista. I've been doing this for
several months, and I know the basic setup is fine, because I can run
any X program without problems. However, just today, after being
logged in for a while, even if I have another X program running (in
background - so I'm using the same xterm I used to launch to other X
program) I get "Error: Can't open display: localhost:10.0" (Yes,
DISPLAY is correctly set to localhost:10.0.)
If I log out of the ssh session and start a new one, X programs work
again, but after a few minutes, it goes back to the error. I am
assuming that if the network (wireless from laptop to router, wired
from router to switch to desktop) were flaky, the ssh connection would
probably be affected, and the other running X program (sometimes emacs,
sometimes balsa email client) would also get dropped, but they both
continue running with no apparent problems.
I'd appreciate any ideas of how to troubleshoot what might be causing
this, since it is certainly annoying.
I've done a fair amount of searching, but everything I've found so far
is a problem with getting either X running at all, or getting ssh to
handle X, neither of which is my problem.
Thanks for any hints or suggestions.
Jack
--
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/
reply other threads:[~2010-09-09 23:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1284075889.11622.1@ffortso4 \
--to=ostroffjh@sbcglobal.net \
--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).