public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: cwcarlsonc@cox.net
Subject: Re: Problem opening remote X applications
Date: Fri, 03 Jan 2014 18:23:00 -0000 [thread overview]
Message-ID: <52C70023.8050204@dronecode.org.uk> (raw)
In-Reply-To: <52C641EF.6070300@cox.net>
On 03/01/2014 04:51, Chris Carlson wrote:
> I just downloaded Cygwin 64-bit for the first time. I've been using Cygwin
> 32-bit for years.
[...]
> I usually "ssh -X <remote>" to a remote Linux machine. I can then read mail
> (thunderbird), edit documents (LibreOffice 3.x), run Chrome, and edit programs
> (Emacs). I'll have half a dozen windows open through the X tunnel provided by
> ssh. Works well and lasts for hours.
>
> After upgrading to Cygwin 64-bit (this last weekend), everything *seems* to be
> okay for a while. After about 20 minutes, though, I can no longer open
> windows remotely. Even though I have thunderbird currently open, when I try
> to run Chrome, I get "(google-chrome:20006): Gtk-WARNING **: cannot open
> display: localhost:10.0". If I try to open xclock from the command line, I get:
>
> xclock
> Error: Can't open display: localhost:10.0
>
> Does anybody know what happened? Why has the tunnel disappeared? It hasn't
> actually disappeared because I'm still running thunderbird through it.
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-twenty-minute-timeout
Use 'ssh -Y'
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
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/
next prev parent reply other threads:[~2014-01-03 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 4:52 Chris Carlson
2014-01-03 18:23 ` Jon TURNEY [this message]
[not found] ` <9WPN1n00H2ceNJh01WPP1l>
2014-01-04 4:39 ` Chris Carlson
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=52C70023.8050204@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cwcarlsonc@cox.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).