Re: Problem opening remote X applications

2014-01-03 Thread Chris Carlson

Wow!  Thanks for the quick response.

That was easy.
Chris


On 1/3/2014 10:23 AM, Jon TURNEY wrote:

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 " 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'




--
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: Problem opening remote X applications

2014-01-03 Thread Jon TURNEY
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 " 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/



Problem opening remote X applications

2014-01-02 Thread Chris Carlson
I just downloaded Cygwin 64-bit for the first time.  I've been using 
Cygwin 32-bit for years.


I'm running on Windows 7, and my Cygwin 32-bit has been working 
reasonably well for a long time.  My only issue with it was a problem it 
had with my Caps Lock key.  For whatever reason, focus would switch 
windows whenever I pressed the Caps Lock key.  The caps would lock, but 
focus would change.


I finally decided to download the latest and greatest to see if it has 
been fixed.  It appears that it is no longer an issue.  Now I have a new 
problem.


I usually "ssh -X " 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.


Thanks for any assistance on this.
Chris


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