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, phlip2005@gmail.com
Subject: Re: ssh -X user@host konsole opens a tunneled konsole, but then the tunnel lapses
Date: Mon, 21 Mar 2011 21:43:00 -0000	[thread overview]
Message-ID: <4D87C64D.9000009@dronecode.org.uk> (raw)
In-Reply-To: <AANLkTi=T2qrye4cUw-GQipsCg-q73=Eb05=cx8HYkbLo@mail.gmail.com>

On 04/03/2011 18:29, Phlip wrote:
> For years I have enjoyed one desktop with everything I need on it.
>
> Then ssh -X stopped working. Sometimes, if I start a remote konsole,

You don't mention if things 'stopped working' spontaneously, or if anything
was changed on either your ssh client or ssh server machine.

> and immediately start some new X window app, it runs thru the tunnel.
>
> But now it trivially bombs, as if there were no remote X to attach to:
>
>   kate: cannot connect to X server localhost:10.0
>
> Is there a timeout setting, somewhere, for the X tunnel? or some
> similar setting to look at?

There is the ForwardX11Timeout setting (see 'man ssh_config'), but that can't
be the explanation for what you are seeing, as that doesn't apply with 'ssh -Y'

> The host is any Win32 or Win64, and the client is Ubuntu...

If you are saying that it doesn't work from any cygwin machine, connecting to
one particular ubuntu server, that should be a pointer that something has
changed on the ubuntu server.

> I also tried manually setting the DISPLAY environmental variable...

If you are setting DISPLAY to point directly at your Cygwin/X server, you will
need to permit access from the remote host, as described in the 'insecure
telnet' section of [1].  Protip: don't do this, it's insecure :-)

On 19/03/2011 15:31, Phlip wrote:
>>>  kate: cannot connect to X server localhost:10.0
> 
>> Have you tried ssh -Y instead of -X ?
> 
> Nope; just tried it, and it didn't work, with the same symptom.

You might find adding '-v' to your ssh command for extra verbosity sheds some
light on what's going on.

> The source is always a CygWin xterm with a little bash inside.
> 
> Got a log file I can look at?

I think you have that backwards.

> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html

^^^^ See this URL.

You didn't attach cygcheck output, so no one knows what version of anything
you are running, so all this advice is purely speculative.

> Documentation:         http://x.cygwin.com/docs/
> FAQ:                   http://x.cygwin.com/docs/faq/

[1] http://x.cygwin.com/docs/ug/using-remote-apps.html

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


  reply	other threads:[~2011-03-21 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 18:29 Phlip
2011-03-19  2:21 ` Phlip
2011-03-19  8:09 ` Csaba Raduly
2011-03-19 15:31   ` Phlip
2011-03-21 21:43     ` Jon TURNEY [this message]
2011-03-23 23:27       ` Phlip

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=4D87C64D.9000009@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=phlip2005@gmail.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).