Re: running openGL application remotely using ssh -X and cygwin/x ,extension "NV-GLX" missing on display "localhost:10.0

[Jon TURNEY]

On 28/04/2014 22:02, Linda Walsh wrote:

Jon TURNEY wrote:

Yes, this should work.


*But*, I'm pretty sure it doesn't anymore since the "Xgl" extension
that was used to transport the openGL commands between client/server
was removed from xorg's Xserver.


You seem to be confusing Xgl (an X server implementation) and GLX (an X 
protocol extension).


While they do contain the same letters in a different order, they are 
very different things.



AIGLX doesn't work with client's native openGL drives when the
DISPLAY isn't local. Instead, it sends full-frame-buffer updates to
simulate what would be happening -- something that "appears" to work
correctly for small OpenGL windows. But is entirely 'faked' (not
really remote openGL that used the Server's acceleration Hardware.

 Which would give you unaccelerated frame-buffer updates to simulate
the effect.  Not quite what used to be available.


This is also totally wrong.

You are (more or less) describing how mesa's direct software rendering 
works (which is usually the default path for remote displays) which is 
completely different to AIGLX (where GL commands are sent via the GLX 
protocol to the X server and rendered using acceleration there)


So, again, please stop spreading misinformation.

I'm sure there are bugs in and limitations with OpenGL and the XWin 
server, but if you have a problem, please don't hijack someone else's 
thread, but report it in sufficient detail for me to try to reproduce it.


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

Re: running openGL application remotely using ssh -X and cygwin/x ,extension "NV-GLX" missing on display "localhost:10.0

[Linda Walsh]

Jon TURNEY wrote:


Yes, this should work.


*But*, I'm pretty sure it doesn't anymore since the "Xgl" extension that was
used to transport the openGL commands between client/server was removed
from xorg's Xserver.

From wikipedia:

Xgl was a display server implementation supporting the X Window System protocol 
designed to take advantage of modern graphics cards via their OpenGL drivers, 
layered on top of OpenGL via glitz. It supported hardware acceleration of all X, 
OpenGL and XVideo applications and graphical effects by a compositing window 
manager such as Compiz or Beryl. The project was started by David Reveman of 
Novell and first released on January 2, 2006. It was removed[1] from the X.org 
server in favor of AIGLX on June 12, 2008.

---

AIGLX doesn't work with client's native openGL drives when the DISPLAY 
isn't
local.  Instead, it sends full-frame-buffer updates to simulate what would be
happening -- something that "appears" to work correctly for small OpenGL 
windows.
But is entirely 'faked' (not really remote openGL that used the Server's
acceleration Hardware.


I'm not entirely clear if the 'extension �NV-GLX� missing' message is a 
warning or an error, but according to the internet it seems to be due to 
having a Nvidia libGL installed on the remote machine, so if all else 
fails you might look at uninstalling the Nvidia proprietary driver and 
libGL, and using mesa instead.


Which would give you unaccelerated frame-buffer updates to simulate
the effect.  Not quite what used to be available.


Note: this isn't a cygwin specific problem.  i.e. people running
xorg's server on a linux box have the same problem -- accelerated+remote
3D graphics seems to be dead.


--
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: running openGL application remotely using ssh -X and cygwin/x ,extension "NV-GLX" missing on display "localhost:10.0

[Biris, Octavian]

I know for a fact that when I ssh from my Ubuntu partition to the
remote machine the application works without crashing. However, when I
use windows 8 and Cygwin X the crash occurs for the same application.
I will install the debugging tools and report my findings to you.

Thanks for looking into this!
-Octavian

On Sat, Apr 26, 2014 at 7:52 AM, Jon TURNEY  wrote:
> On 24/04/2014 23:45, Biris, Octavian wrote:
>>
>> I am attempting to  run an opengl application remptely to a ubuntu
>> linux machine from my windows 8 machine.
>> To do so  I start the cygwin console, call startxwin.
>> Running glxinfo | grep OpenGL returns the vendor of my graphics card,
>> NVIDIA.
>>
>> glxinfo |grep OpenGL
>> OpenGL vendor string: NVIDIA Corporation
>> OpenGL renderer string: GeForce GTX 580/PCIe/SSE2
>> OpenGL version string: 1.4 (4.4.0)
>> OpenGL extensions:
>> Then I ssh on the ubuntu machine using -X -C as the parameters.
>> When attempting to start the application the console reads
>> extension "NV-GLX" missing on display "localhost:10.0".
>> Afterwards, the cygwin/X server crashes and I have to restart it.I
>> attached the log from
>> /var/log/Xwin/XWin.0.log
>
>
> Thanks for the bug report.
>
> I'm afraid that the log doesn't contain enough information for me to
> identify the cause of the crash.
>
> Can you install the xorg-server-debuginfo package and try again?
>
> I also have been working on a tool to automate sending better crash
> information using minidumps.  If you would like to try that, download it
> from [1] (anonymous ftp) and put it into /usr/bin and reproduce your crash
> again.
>
> [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe
>
>
>> Does cygwin/x support running OpenGL applications remotely? Am I
>> missing something? Do I have to install the mesa-utils libraries on
>> the remote machine?
>
>
> Yes, this should work.
>
> I'm not entirely clear if the 'extension "NV-GLX" missing' message is a
> warning or an error, but according to the internet it seems to be due to
> having a Nvidia libGL installed on the remote machine, so if all else fails
> you might look at uninstalling the Nvidia proprietary driver and libGL, and
> using mesa instead.
>
> --
> 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/

Re: running openGL application remotely using ssh -X and cygwin/x ,extension "NV-GLX" missing on display "localhost:10.0

[Jon TURNEY]

On 24/04/2014 23:45, Biris, Octavian wrote:

I am attempting to  run an opengl application remptely to a ubuntu
linux machine from my windows 8 machine.
To do so  I start the cygwin console, call startxwin.
Running glxinfo | grep OpenGL returns the vendor of my graphics card, NVIDIA.

glxinfo |grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 580/PCIe/SSE2
OpenGL version string: 1.4 (4.4.0)
OpenGL extensions:
Then I ssh on the ubuntu machine using -X -C as the parameters.
When attempting to start the application the console reads
extension "NV-GLX" missing on display "localhost:10.0".
Afterwards, the cygwin/X server crashes and I have to restart it.I
attached the log from
/var/log/Xwin/XWin.0.log


Thanks for the bug report.

I'm afraid that the log doesn't contain enough information for me to 
identify the cause of the crash.


Can you install the xorg-server-debuginfo package and try again?

I also have been working on a tool to automate sending better crash 
information using minidumps.  If you would like to try that, download it 
from [1] (anonymous ftp) and put it into /usr/bin and reproduce your 
crash again.


[1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe


Does cygwin/x support running OpenGL applications remotely? Am I
missing something? Do I have to install the mesa-utils libraries on
the remote machine?


Yes, this should work.

I'm not entirely clear if the 'extension “NV-GLX” missing' message is a 
warning or an error, but according to the internet it seems to be due to 
having a Nvidia libGL installed on the remote machine, so if all else 
fails you might look at uninstalling the Nvidia proprietary driver and 
libGL, and using mesa instead.


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

running openGL application remotely using ssh -X and cygwin/x ,extension "NV-GLX" missing on display "localhost:10.0

[Biris, Octavian]

Hello there!
I am attempting to  run an opengl application remptely to a ubuntu
linux machine from my windows 8 machine.
To do so  I start the cygwin console, call startxwin.
Running glxinfo | grep OpenGL returns the vendor of my graphics card, NVIDIA.

glxinfo |grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 580/PCIe/SSE2
OpenGL version string: 1.4 (4.4.0)
OpenGL extensions:
Then I ssh on the ubuntu machine using -X -C as the parameters.
When attempting to start the application the console reads
extension "NV-GLX" missing on display "localhost:10.0".
Afterwards, the cygwin/X server crashes and I have to restart it.I
attached the log from
/var/log/Xwin/XWin.0.log

Does cygwin/x support running OpenGL applications remotely? Am I
missing something? Do I have to install the mesa-utils libraries on
the remote machine?
Thanks so much!

-Octavian


XWin.0.log
Description: Binary data
--
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: ssh -X : connect /tmp/.X11-unix/X0: No such file or directory

[Ronald Fischer]

On Fri, Apr 20, 2012, at 19:53, Jon TURNEY wrote:
> On 20/04/2012 11:43, Ronald Fischer wrote:
> > My setup so far (which is working well), was to use Xming as X-Server
> > and putty for logging into our Solaris hosts via ssh. Since I have
> > Cygwin installed, I thought I could use its ssh equally well, so I
> > exported the ssh key from putty to the format understood by ssh, and
> > used the following bash command to login to the Solaris host:
> > 
> >   DISPLAY=:0.0 TERM=xterm  ssh -p 22 -K -X -i MyPrivateKeyFile 
> >   MyUserName@SolarisHost
> > 
> > When I now try to start an X application, I get an error message like
> > this 
> > 
> >  connect /tmp/.X11-unix/X0: No such file or directory 
> >  XIO:  fatal IO error 131 (Connection reset by peer) on X server
> >  "SolarisHost:239.0"
> >after 0 requests (0 known processed) with 0 events remaining.
> 
> I think I know what's going on here.
> 
> The solution should be to use DISPLAY=localhost:0.0 instead, which means
> to
> connect to the X server for display 0 via TCP/IP, which the Xming X
> server
> should be listening on.

Nice idea, but the result is, that I just get a different error message.
Now it becomes:

 connect localhost port 6000: Connection refused 
 X connection to SolarisHost:217.0 broken (explicit kill or server
 shutdown).

>From the FAQ, I see that port 6000 is the default. Could it be that I
need to specify somehow a non-standard port? 

Ronald
-- 
Ronald Fischer 
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+   (cited after Peter van der Linden)


--
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: ssh -X : connect /tmp/.X11-unix/X0: No such file or directory

[Jon TURNEY]

On 20/04/2012 11:43, Ronald Fischer wrote:
> My setup so far (which is working well), was to use Xming as X-Server
> and putty for logging into our Solaris hosts via ssh. Since I have
> Cygwin installed, I thought I could use its ssh equally well, so I
> exported the ssh key from putty to the format understood by ssh, and
> used the following bash command to login to the Solaris host:
> 
>   DISPLAY=:0.0 TERM=xterm  ssh -p 22 -K -X -i MyPrivateKeyFile 
>   MyUserName@SolarisHost
> 
> When I now try to start an X application, I get an error message like
> this 
> 
>  connect /tmp/.X11-unix/X0: No such file or directory 
>  XIO:  fatal IO error 131 (Connection reset by peer) on X server
>  "SolarisHost:239.0"
>after 0 requests (0 known processed) with 0 events remaining.

I think I know what's going on here.

cygwin ssh understands DISPLAY=:0.0 to mean to connect to the X server for
display 0 via a local (UNIX domain) socket, named /tmp/.X11-unix/X0

The Xming X server, not being a cygwin application, cannot listen on that 
socket.

The solution should be to use DISPLAY=localhost:0.0 instead, which means to
connect to the X server for display 0 via TCP/IP, which the Xming X server
should be listening on.

See FAQ 1.6 [1] for more details.

[1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#display-and-screen

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

ssh -X : connect /tmp/.X11-unix/X0: No such file or directory

[Ronald Fischer]

My setup so far (which is working well), was to use Xming as X-Server
and putty for logging into our Solaris hosts via ssh. Since I have
Cygwin installed, I thought I could use its ssh equally well, so I
exported the ssh key from putty to the format understood by ssh, and
used the following bash command to login to the Solaris host:

  DISPLAY=:0.0 TERM=xterm  ssh -p 22 -K -X -i MyPrivateKeyFile 
  MyUserName@SolarisHost

When I now try to start an X application, I get an error message like
this 

 connect /tmp/.X11-unix/X0: No such file or directory 
 XIO:  fatal IO error 131 (Connection reset by peer) on X server
 "SolarisHost:239.0"
   after 0 requests (0 known processed) with 0 events remaining.

Further investigation reveals the following:

(1) I start my putty login, and find that on the remote host DISPLAY is
set to (say): SolarisHost:261.0
Starting X applications works fine.

(2) I start my open ssh login from Cygwin, and find that the DISPLAY
variable is set to a different value, for example SolarisHost:239.0 .
Starting X applications does not work.

(3) In the latter shell, I export DISPLAY=SolarisHost:261.0 . Starting X
applications now works. 

The fact that each login produces a different value for DISPLAY, is
normal behaviour. Even when starting several putty sessions, each gets a
different value for DISPLAY, and X apps work in all of them.

It seems that by doing the ssh connection via putty, something is done
which is missing from my ssh started from Cygwin. 

BTW, I also tried to use -Y instead of -X in my ssh invocation, but with
no effect.

Ronald
-- 
Ronald Fischer 
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+   (cited after Peter van der Linden)


--
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: ssh -X user@host konsole opens a tunneled konsole, but then the tunnel lapses

[Phlip]

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

Tx guys - either the -v or the -Y did it.

(Yes yes I know -v is just the debugging trace. Maybe it changes the timing!)

--
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: ssh -X user@host konsole opens a tunneled konsole, but then the tunnel lapses

[Jon TURNEY]

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/

Re: ssh -X user@host konsole opens a tunneled konsole, but then the tunnel lapses

[Phlip]

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

The source is always a CygWin xterm with a little bash inside.

Got a log file I can look at?

-- 
  Phlip
  http://c2.com/cgi/wiki?ZeekLand

--
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: ssh -X user@host konsole opens a tunneled konsole, but then the tunnel lapses

[Csaba Raduly]

Hi Philip,

On Fri, Mar 4, 2011 at 7:29 PM, Phlip  wrote:
> CygWinners:
>
> 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,
> 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
>

Have you tried ssh -Y instead of -X ?

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
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: ssh -X user@host konsole opens a tunneled konsole, but then the tunnel lapses

[Phlip]

Bump?

Should I try a noisier forum, or one for a different layer of the system?

On Fri, Mar 4, 2011 at 10:29 AM, Phlip  wrote:
> CygWinners:
>
> 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,
> 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?
>
> The host is any Win32 or Win64, and the client is Ubuntu...
>
> I also tried manually setting the DISPLAY environmental variable...
>
> --
>   Phlip
>   http://c2.com/cgi/wiki?ZeekLand
>



-- 
  Phlip
  http://c2.com/cgi/wiki?ZeekLand

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

ssh -X user@host konsole opens a tunneled konsole, but then the tunnel lapses

[Phlip]

CygWinners:

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,
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?

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

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

-- 
  Phlip
  http://c2.com/cgi/wiki?ZeekLand

--
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: 1.7.2: ssh -X unresponsive until xauth PPID killed

[Mark McConnell]

2010/3/29 Mark McConnell :
> I turned off Data Execution Protection for all except crucial Windows
> programs, and the XWin problems I described were resolved.
>
> Thanks for your patience,
>
> Mark
> --

I discovered afterward that this is related to FAQ #14.  This Server
2008 is running Terminal Services, and that is the key fact.

http://www.cygwin.com/faq/faq.setup.html#faq.setup.setup-fails-on-ts

I'm sorry that faq escaped my attention.  I didn't recognize the
connection, since I set up Cygwin on a local console, not through
Terminal Services; but now the relationship is obvious to me.

Mark
--

--
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: 1.7.2: ssh -X unresponsive until xauth PPID killed

[Mark McConnell]

I turned off Data Execution Protection for all except crucial Windows
programs, and the XWin problems I described were resolved.

Thanks for your patience,

Mark
--

--
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: 1.7.2: ssh -X unresponsive until xauth PPID killed

[Mark McConnell]

2010/3/29 Jon TURNEY :
> On 27/03/2010 21:53, Mark McConnell wrote:
>>
>> (Please forgive the repost - this version has the attachments mentioned)
>>
>> After installing Cygwin 1.7.2 for the first time on Windows Server 2008
>> SP2,
>> I discovered that I could not connect to a remote host using Cygwin's ssh,
>> if X is forwarded.
>>
>> ssh -X host or ssh -Y host :  program becomes unresponsive.
>>
>> I've attached the output of cygcheck -s -v -r to this message, and
>> /var/log/XWin.0.log.  I should mention as an aside that there are other
>> clues that my Cygwin installation is flawed (a local gvim gui will not
>> display, man dumps core).
>
> Given that, I'm thinking that the problem you describe with the xauth
> subprocess is probably symptomatic of some deeper problem with you
> installation or environment.
>
> You should probably ask for help on the main cygwin list.
>
>
>> Below, I describe two experiments that indicate that my X forwarding
>> problem
>> is somehow related to xauth* and its PPID:
>>
>> ### 'ssh -X host gui'  displays if the PPID of xauth* is killed ###
>> First, I open a new mintty window within the Cygwin environment and issue
>> the command to start gvim on the remote server, using the forwarded X
>> display.  No gui is displayed.  The cursor returns below the prompt.  ^d
>> or
>> ^c do not terminate the process ( however, I can suspend it from that
>> window
>> by typing ^z, and I can return it to the foreground with "fg" ).
>
> --
> Jon TURNEY
> Volunteer Cygwin/X X Server maintainer

Thank you, Jon.  I'll give some thought to how to summarize the
various problems I'm experiencing and send that to the main list.

Mark
--

--
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: 1.7.2: ssh -X unresponsive until xauth PPID killed

[Jon TURNEY]

On 27/03/2010 21:53, Mark McConnell wrote:

(Please forgive the repost - this version has the attachments mentioned)

After installing Cygwin 1.7.2 for the first time on Windows Server 2008 SP2,
I discovered that I could not connect to a remote host using Cygwin's ssh,
if X is forwarded.

ssh -X host or ssh -Y host :  program becomes unresponsive.

I've attached the output of cygcheck -s -v -r to this message, and
/var/log/XWin.0.log.  I should mention as an aside that there are other
clues that my Cygwin installation is flawed (a local gvim gui will not
display, man dumps core).


Given that, I'm thinking that the problem you describe with the xauth 
subprocess is probably symptomatic of some deeper problem with you 
installation or environment.


You should probably ask for help on the main cygwin list.



Below, I describe two experiments that indicate that my X forwarding problem
is somehow related to xauth* and its PPID:

### 'ssh -X host gui'  displays if the PPID of xauth* is killed ###
First, I open a new mintty window within the Cygwin environment and issue
the command to start gvim on the remote server, using the forwarded X
display.  No gui is displayed.  The cursor returns below the prompt.  ^d or
^c do not terminate the process ( however, I can suspend it from that window
by typing ^z, and I can return it to the foreground with "fg" ).


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

1.7.2: ssh -X unresponsive until xauth PPID killed

[Mark McConnell]

After installing Cygwin 1.7.2 for the first time on Windows Server 2008 SP2,
I discovered that I could not connect to a remote host using Cygwin's ssh,
if X is forwarded.

ssh -X host or ssh -Y host :  program becomes unresponsive.

I've attached the output of cygcheck -s -v -r to this message, and
/var/log/XWin.0.log.  I should mention as an aside that there are other
clues that my Cygwin installation is flawed (a local gvim gui will not
display, man dumps core).

Below, I describe two experiments that indicate that my X forwarding problem
is somehow related to xauth* and its PPID:

### 'ssh -X host gui'  displays if the PPID of xauth* is killed ###
First, I open a new mintty window within the Cygwin environment and issue
the command to start gvim on the remote server, using the forwarded X
display.  No gui is displayed.  The cursor returns below the prompt.  ^d or
^c do not terminate the process ( however, I can suspend it from that window
by typing ^z, and I can return it to the foreground with "fg " ).

pt0 $ ssh -X dasftp gvim
|

I open a second mintty instance and look at the process running locally:
pt1 $ ps
  PIDPPIDPGID WINPID  TTY  UIDSTIME COMMAND
 4532   14532   5296  con 11137 11:40:42 /usr/bin/XWin
 343245323432   4244? 11137 13:15:21 /usr/bin/mintty
 336434323364   36880 11137 13:15:21 /usr/bin/bash
 597233645972   24360 11137 13:15:39 /usr/bin/ssh
 579259725972   57920 11137 13:15:39 /usr/bin/sh
 263257925972   25480 11137 13:15:39 /usr/bin/xauth

In the second terminal I kill the sh* process that is the parent of xauth*.
The remote gvim gui immediately appears.  xauth* is now running with PPID 1

pt1 $ ps | grep /usr/bin/sh | sed -e 's/^\s*//' | kill `sed -e 's/\s.*//'` ;
ps
  PIDPPIDPGID WINPID  TTY  UIDSTIME COMMAND
 4532   14532   5296  con 11137 11:40:42 /usr/bin/XWin
 343245323432   4244? 11137 13:15:21 /usr/bin/mintty
 336434323364   36880 11137 13:15:21 /usr/bin/bash
 597233645972   24360 11137 13:15:39 /usr/bin/ssh
 2632   15972   25480 11137 13:15:39 /usr/bin/xauth

After closing gvim, I take a peek at the processes left behind.  ssh* has
terminated, bash* has been idle, xauth* continues to run even if X is
closed.  Its PPID has changed to 1

pt1 $ ps
  PIDPPIDPGID WINPID  TTY  UIDSTIME COMMAND
 4532   14532   5296  con 11137 11:40:42 /usr/bin/XWin
 343245323432   4244? 11137 13:15:21 /usr/bin/mintty
I336434323364   36880 11137 13:15:21 /usr/bin/bash
 2632   15972   25480 11137 13:15:39 /usr/bin/xauth

pt1 $ kill 2632
bash: kill: (2632) - Resource temporarily unavailable

Summarizing: SSH authentication succeeds but the ssh* is unresponsive when
started with X forwarding.   Killing the PPID of xauth* leaves it running in
the background.  xauth* will remain running even after the X server is
closed.  To kill the zombie xauth* I use Windows Task Manager.

## 'ssh -X host' succeeds after PPID of xauth* is killed ##
Here's a  simplified version of the experiment.

In terminal 1:
pt0 $ ssh -v -v -X dasftp 2> ssh.out

In terminal 2, I kill the PPID of xauth* (/usr/bin/sh):
pt1 $ ps | grep /usr/bin/sh | sed -e 's/^\s*//' | kill `sed -e 's/\s.*//'` ;

In terminal 1 (connected to 'host'):
Welcome to dasftp
pt3 $

I have attached ssh.out also, which is the debug output of "ssh -v -v -X
host". I can provide a much more detailed description of the steps I've
followed, if that would be helpful.

Many thanks,
Mark
--

--
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: ssh -x

[Holger Krull]

Ruth Ivimey-Cook schrieb:

 > There is another option: set up an LBX connection. This requires a process
> (called LBX) that runs on the machine running the normal X server; you then
> connect your clients to LBX.
> 
> LBX is "Low Bandwidth X" and is a protocol-specific compression algorithm 
> which
> works reasonably well. It may help to use normal compress on the result, but I
> doubt it.
> 
> The downside is there is no automatic method of setting it up, unlike for ssh
> -X

Yes, the low bandwith extension does help. The nx proxy from nomachine.com is 
working on the same principle and more efficient (including image caching). 

--
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: ssh -x

[Ruth Ivimey-Cook]

 

> The encryption doesn't matter. It is the latency of your 
> connection that matters (ping time), because the X proctocol 
> isn't very efficient. 

There is another option: set up an LBX connection. This requires a process
(called LBX) that runs on the machine running the normal X server; you then
connect your clients to LBX.

LBX is "Low Bandwidth X" and is a protocol-specific compression algorithm which
works reasonably well. It may help to use normal compress on the result, but I
doubt it.

The downside is there is no automatic method of setting it up, unlike for ssh
-X

Regards,

Ruth


--
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: ssh -x

[Holger Krull]

Scott Fordin schrieb:
> Holger Krull wrote:
>>> /usr/X11R6/bin/xhost +
>>
>> No you don't have to, if you use ssh to tunnel the X11 connection.
>> (It would be localhost anyway and not the linux_machine_name). Try to
>> understand the difference between tunneling and a remote connection.
> 
> I understand what you're saying. All I know is that for some
> applications, like Emacs and Arbortext Epic, it seems I have
> to explicitly add the remote machine to my local X access list
> for the applications to display on my local machine. Moreover,
> for Epic to work, I have to explicitly set the DISPLAY variable
> on the remote machine. Dunno. It works for me, but YMMV.

If you do this, you are not using the forwarding mechanism of ssh. 

--
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: ssh -x

[Scott Fordin]

Holger Krull wrote:

/usr/X11R6/bin/xhost +


No you don't have to, if you use ssh to tunnel the X11 connection.
(It would be localhost anyway and not the linux_machine_name). Try to
understand the difference between tunneling and a remote connection.


Hi, Holger,

I understand what you're saying. All I know is that for some
applications, like Emacs and Arbortext Epic, it seems I have
to explicitly add the remote machine to my local X access list
for the applications to display on my local machine. Moreover,
for Epic to work, I have to explicitly set the DISPLAY variable
on the remote machine. Dunno. It works for me, but YMMV.

Scott

--
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: ssh -x

[Holger Krull]

Larry Hall (Cygwin X) schrieb:
> Holger Krull wrote:
>> Your guess is right. You have to start a local X11 server (startx). And
>> set DISPLAY before you start ssh. 
> 
> Setting DISPLAY is not necessary with 'ssh -X' or 'ssh -Y'.  More than
> that,
> setting DISPLAY will likely cause the X forwarding to not work as expected.
> For more info, read the "X11 FORWARDING" section of the 'ssh' man page.
> 

I was writing about the DISPLAY for the ssh process. 


--
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: ssh -x

[Larry Hall (Cygwin X)]

Holger Krull wrote:

Marco Meoni schrieb:

hi, I'm new with cygwin. I've mainly installed it to connect to a linux
server running GUI applications. In fact, I've read that with X11
forwarding (ssh -X) I can run remote applications and display the GUI
on my pc running cygwin.

Unfortunately I get errors like "can't open display". Does anybody know
what do I have to setup before? (i guess start X11 server on my local
pc)


Your guess is right. You have to start a local X11 server (startx). And
set DISPLAY before you start ssh. 


Setting DISPLAY is not necessary with 'ssh -X' or 'ssh -Y'.  More than that,
setting DISPLAY will likely cause the X forwarding to not work as expected.
For more info, read the "X11 FORWARDING" section of the 'ssh' man page.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

--
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: ssh -x

[Holger Krull]

Marco Meoni schrieb:
> As far as I understand, with X11 tunneling I've an encrypted connection, 
> whilst
> with remote connection I don't.

That is right.

> Besides, I can easily pass through several machines in one shot (my pc ssh
> server1 that ssh server2 and finally get back the GUI to my pc)
> But what from the speed point of view? Too many encrypting steps?

The encryption doesn't matter. It is the latency of your connection that 
matters (ping time), because the X proctocol isn't very efficient. 
You could add compression to the ssh connection if your bandwidth is low (-C), 
but that would also increase latency. 
To reduce the X11 overhead you can use lbxproxy or the nxserver if these exist 
on the remote Unix/Linux installation.


--
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: ssh -x

[Marco Meoni]

guys, thank you for the answers.
This game is very cool. I got amazed! It works great!
As far as I understand, with X11 tunneling I've an encrypted connection, whilst
with remote connection I don't.
Besides, I can easily pass through several machines in one shot (my pc ssh
server1 that ssh server2 and finally get back the GUI to my pc)
But what from the speed point of view? Too many encrypting steps?
Other advantages in respect of remote connection / vnc ?

Cheers,
Marco  


--
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: ssh -x

[Holger Krull]

Scott Fordin schrieb:
> Holger Krull wrote:
>> Marco Meoni schrieb:

>>> know what do I have to setup before? (i guess start X11 server on
>>> my local pc)
>>
>> Your guess is right. You have to start a local X11 server (startx).
>> And set DISPLAY before you start ssh. Also remember that some
>> applications need ssh -Y.
> 
> You also may need to use xhost to add the remote machine to
> the access control list on your local machine; for example,
> in your Cygwin shell:
> 
>/usr/X11R6/bin/xhost +

No you don't have to, if you use ssh to tunnel the X11 connection. (It would be 
localhost anyway and not the linux_machine_name). Try to understand the 
difference between tunneling and a remote connection. 




--
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: ssh -x

[Scott Fordin]

Holger Krull wrote:

Marco Meoni schrieb:

hi, I'm new with cygwin. I've mainly installed it to connect to a
linux server running GUI applications. In fact, I've read that with
X11 forwarding (ssh -X) I can run remote applications and display
the GUI on my pc running cygwin.

Unfortunately I get errors like "can't open display". Does anybody
know what do I have to setup before? (i guess start X11 server on
my local pc)


Your guess is right. You have to start a local X11 server (startx).
And set DISPLAY before you start ssh. Also remember that some
applications need ssh -Y.


You also may need to use xhost to add the remote machine to
the access control list on your local machine; for example,
in your Cygwin shell:

   /usr/X11R6/bin/xhost +

Some applications also don't seem to work with ssh -X or
ssh -Y. For those apps, you may need to explicitly export
the remote machine display to your local machine; for
example, from your Linux box:

   export DISPLAY=:0.0

Scott




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




--
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: ssh -x

[Holger Krull]

Marco Meoni schrieb:
> hi, I'm new with cygwin.
> I've mainly installed it to connect to a linux server running GUI 
> applications.
> In fact, I've read that with X11 forwarding (ssh -X) I can run remote
> applications and display the GUI on my pc running cygwin.
> 
> Unfortunately I get errors like "can't open display". Does anybody know what 
> do
> I have to setup before? (i guess start X11 server on my local pc)

Your guess is right.
You have to start a local X11 server (startx). And set DISPLAY before you start 
ssh. Also remember that some applications need 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/

ssh -x

[Marco Meoni]

hi, I'm new with cygwin.
I've mainly installed it to connect to a linux server running GUI applications.
In fact, I've read that with X11 forwarding (ssh -X) I can run remote
applications and display the GUI on my pc running cygwin.

Unfortunately I get errors like "can't open display". Does anybody know what do
I have to setup before? (i guess start X11 server on my local pc)

thank you in advance

Marco


--
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: How to run _X_ Session from RH8 via ssh -X?

[Larry Hall (Cygwin X)]

Brett Serkez wrote:

But now I just realized the obvious: Only X GUIS work and not windows.

Is this correct?


Yes!


I assume I can tunnel rdesktop the same way I tunnel vnc? I guess I'll try
tunneling both vnc and rdesktop  next.


I've heard this works, but have not tried personally.  If you get this
working, can you post your ssh command with the port(s) you needed to
forward?


I used to use the following all the time to access my Windows machine
remotely:

ssh -f -L 5901:localhost:5900 -N -C -o Compression=yes -o CompressionLevel=9 


vncviewer &

YMMV.

Obviously, you need to make sure that the port ssh is using is open
through any firewall.

None of this is really Cygwin-specific so further discussion on this l
list along this line is really off-topic though.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746

--
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: How to run _X_ Session from RH8 via ssh -X?

[Brett Serkez]

> But now I just realized the obvious: Only X GUIS work and not windows.
>
> Is this correct?

Yes!

> I assume I can tunnel rdesktop the same way I tunnel vnc? I guess I'll try
> tunneling both vnc and rdesktop  next.

I've heard this works, but have not tried personally.  If you get this
working, can you post your ssh command with the port(s) you needed to
forward?

Brett

--
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: How to run _X_ Session from RH8 via ssh -X?

[Siegfried Heintze]

Thanks Dan and Rene! It works.

But now I just realized the obvious: Only X GUIS work and not windows. 

Is this correct?

I assume I can tunnel rdesktop the same way I tunnel vnc? I guess I'll try
tunneling both vnc and rdesktop  next.

Siegfried


--
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: How to run _X_ Session from RH8 via ssh -X?

[Doug VanLeuven]

Siegfried Heintze wrote:

[snip]
Why does  /usr/X11R6/bin/xclock still say "Error can't open display:"?

That looks like an explicit unsetting of DISPLAY, i.e. somewhere, probably

your

.profile/.bashrc/.bash_profile, has a "unset DISPLAY".

Starting in Cygwin:
$ echo $DISPLAY
:0
$ ssh -X [EMAIL PROTECTED]
# echo $DISPLAY
localhost:10.0

Notice that ssh created a pseudo display that will be used to tunnel the X
protocol back to your local X server.


I did 
ssh -X [EMAIL PROTECTED]

ls -A -1 | xargs grep -n DISPLAY *
echo $DISPLAY

The only place DISPLAY occurred (in the output) was in the .bash_history
file. Echo $DISPLAY gave a blank line only.

Any other suggestions?



On linux system:
/etc/ssh/sshd_config
X11Forwarding yes
/etc/ssh/ssh_config
ForwardX11 yes

On cygwin system:
/etc/defaults/etc/sshd_config
X11Forwarding yes
/etc/defaults/etc/ssh_config
ForwardX11 yes

Doug

--
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: How to run _X_ Session from RH8 via ssh -X?

[René Berber]

Siegfried Heintze wrote:
>>> [snip]
> echo $DISPLAY
>
> Any other suggestions?

Check /etc/sshd_config on the server, configure it to forward X11:

# X11 tunneling options
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes

After restarting sshd try:

ssh -X [EMAIL PROTECTED] 'echo $DISPLAY'
-- 
René Berber


--
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: How to run _X_ Session from RH8 via ssh -X?

[Siegfried Heintze]

> > [snip]
> > Why does  /usr/X11R6/bin/xclock still say "Error can't open display:"?
> 
> That looks like an explicit unsetting of DISPLAY, i.e. somewhere, probably
your
> .profile/.bashrc/.bash_profile, has a "unset DISPLAY".
> 
> Starting in Cygwin:
> $ echo $DISPLAY
> :0
> $ ssh -X [EMAIL PROTECTED]
> # echo $DISPLAY
> localhost:10.0
> 
> Notice that ssh created a pseudo display that will be used to tunnel the X
> protocol back to your local X server.

I did 
ssh -X [EMAIL PROTECTED]
ls -A -1 | xargs grep -n DISPLAY *
echo $DISPLAY

The only place DISPLAY occurred (in the output) was in the .bash_history
file. Echo $DISPLAY gave a blank line only.

Any other suggestions?
Sieg 


--
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: How to run _X_ Session from RH8 via ssh -X?

[René Berber]

Siegfried Heintze wrote:
> [snip]
> Why does  /usr/X11R6/bin/xclock still say "Error can't open display:"?

That looks like an explicit unsetting of DISPLAY, i.e. somewhere, probably your
.profile/.bashrc/.bash_profile, has a "unset DISPLAY".

Starting in Cygwin:
$ echo $DISPLAY
:0
$ ssh -X [EMAIL PROTECTED]
# echo $DISPLAY
localhost:10.0

Notice that ssh created a pseudo display that will be used to tunnel the X
protocol back to your local X server.
-- 
René Berber


--
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: How to run _X_ Session from RH8 via ssh -X?

[Siegfried Heintze]

[snip]

> > > However, I cannot seem to start an X session from my "ssh  -X -p 892
> > > [EMAIL PROTECTED]" session. I tried running "explorer ." and
that
> > > just hung. OK, that was not an X program.  Then I tried
> > > /usr/X11R6/bin/xclock and it said it could not open the display.
Having
> > > already done a xhost+  before running ssh I tried
export
> > > DISPLAY=:0.0 but that did not help: it still could
not
> > > open the display.
> 
> If you are using ssh -X or -Y you don't need to set DISPLAY, in fact ssh
already
> did set it.  But if you set DISPLAY then X uses the normal ports and those
will
> have to be opened/redirected on the firewall.
> 
> [snip]
> > > winCheckDisplayNumber - Cygwin/X is already running on display 0
> 
> It was running already but it's not needed unless you want to use VNC.

Well what am I doing wrong? I forgot to mention: the firewall guarding the
windows machine must have the necessary ports open or I would not be able to
establish a console window on it.

Why does  /usr/X11R6/bin/xclock still say "Error can't open display:"?

Thanks,
Siegfried


--
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: How to run _X_ Session from RH8 via ssh -X? How to run vnc via ssh?

[René Berber]

Siegfried Heintze wrote:
[snip]
> > (2) For reasons I don't understand, there was a conflict between my router's
> > sshd and my cygwin's sshd so I resolved the problem by changing the cygwin's
> > configuration file to start sshd on a different port. Now, using a Red Hat 8
> > client, I can use both rdesktop and ssh to create two different simultaneous
> > sessions on my win2003 server.
> >
> > However, I cannot seem to start an X session from my "ssh  -X -p 892
> > [EMAIL PROTECTED]" session. I tried running "explorer ." and that
> > just hung. OK, that was not an X program.  Then I tried
> > /usr/X11R6/bin/xclock and it said it could not open the display. Having
> > already done a xhost+  before running ssh I tried export
> > DISPLAY=:0.0 but that did not help: it still could not
> > open the display.

If you are using ssh -X or -Y you don't need to set DISPLAY, in fact ssh already
did set it.  But if you set DISPLAY then X uses the normal ports and those will
have to be opened/redirected on the firewall.

> > Do I need to punch a whole in my client's firewall? I doubt the will let me
> > do that.

Not if you only use ssh.  But take in consideration that you changed ssh to use
port 892, that one is the one that will have to be opened.

> > Don't I need to start the xserver?

In the remote system? no.

[snip]
> > winCheckDisplayNumber - Cygwin/X is already running on display 0

It was running already but it's not needed unless you want to use VNC.

> > (3) What about vnc? I have installed RealVNC on both the RH8 client and the
> > Windows 2003 server.

For VNC you'll need to open port 5901 (or 5801 for http); this is only for the
first window, it really is 5900 + display number, in case you have more than one
user connecting to the same machine.

> > Is there also a cygwin VNC? I don't remember seeing one.

No.

> > Can I make vnc tunnel thru ssh? Would I use the -L or the -R qualifier
> > on ssh? What would that look like?

Yes.  You have to start the VNC server and then (assuming display 1 is used):

client machine# ssh -NfC -L 5901:server.name.or.ip:15901 [EMAIL PROTECTED]

server machine# ssh -gN -L 15901:localhost:5901 [EMAIL PROTECTED]

The numbers may have to be changed (as I said above) depending on what starting
the server reported as display number or how is setup to start if you start it
from the X server.

On the client you use as VNC server "localhost:1".

HTH
-- 
René Berber


--
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: a feathiable solution displaying Windows program on Linux via ssh / X?

[Alexander Gottwald]

On Wed, 28 Sep 2005, Bobber Cheng wrote:

> Hi, ago
> 
> I use CYGWIN_NT-5.1 with gcc 3.4.4 to compile cygpeace-0.0.0. 
> 
> tut it failed with error:
> 
> ./configure
> .
> 
> ./make
> ...
> dll/ui.so/X11.cc: In member function `virtual HWND__* 
> X11::GetForegroundWindow()
> ':
> dll/ui.so/X11.cc:295: error: invalid conversion from `uint32_t*' to `UINT*'
> dll/ui.so/X11.cc:295: error:   initializing argument 2 of `virtual 
> HWND__** X11:
> :GetChildWindowHandles(Window, UINT*)'

I think you could just add a explicit cast (UINT*) at the offending position. 
I've not compiled it for some time now. Mabye the definitions from  w32api 
have changed.

BTW: the -bin package should contain binaries which you could use for testing.

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

--
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: a feathiable solution displaying Windows program on Linux via ssh / X?

[Bobber Cheng]

Hi, ago

I use CYGWIN_NT-5.1 with gcc 3.4.4 to compile cygpeace-0.0.0. 
<http://www.freedesktop.org/%7Eago/cygpeace/cygpeace-0.0.0-bin.tar.bz2>

tut it failed with error:

./configure
.

./make
...
dll/ui.so/X11.cc: In member function `virtual HWND__* 
X11::GetForegroundWindow()

':
dll/ui.so/X11.cc:295: error: invalid conversion from `uint32_t*' to `UINT*'
dll/ui.so/X11.cc:295: error:   initializing argument 2 of `virtual 
HWND__** X11:

:GetChildWindowHandles(Window, UINT*)'

Bests,
Bobber Cheng

Alexander Gottwald wrote:


On Thu, 22 Sep 2005, Bobber Cheng wrote:

 

Had anyone found a feathiable solution displaying Windows program on 
Linux via ssh / X? If the answser is no, i beg X gurus to give me any 
advice how to implement it. Wine and VNC are not my choice.
   



An alternative to Terminal client or cytrix is rdesktop. But besides that
there is no working solution to wrap windows programs with X11. You might
want to take a look at cygpeace which is not much more than a prove of 
concept which allowed to export winmine over x11.


http://www.freedesktop.org/~ago/cygpeace/

Before begging X gurus (which btw is the wrong group to ask) you should
check the win32-x11 archives http://sourceware.org/ml/win32-x11/ starting 
with July - September, 2002 until July - September, 2004. Some techniques 
for wrapping and redirecting windows GDI calls to X11 were discussed there

but most of the initial activity vaporized after few months.

Basicly there are a few ways which might work:

- build a display driver which uses X11 as backend
 x11_drv from wine might provide the conversion to X11 calls
- wrap GDI calls from applications with own, X11 aware implementations
 cygpeace aproach
- Check how Terminal Client works and implement a backend which uses X11 
 instead of RDP


bye
ago
BTW: Use rdesktop.
 




--
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: a feathiable solution displaying Windows program on Linux via ssh / X?

[Hr. Daniel Mikkelsen]

On Thu, 22 Sep 2005, Bobber Cheng wrote:

> Wine is a win32 emulator in Unix, *wine in cygwin* need to install lot
> of thing. The worst is that wine is currently under heavy development,
> many win32 apps could not run on it. e.g. IE.

Wine runs IE:

  http://frankscorner.org/index.php?p=ie6

-- 
Daniel Mikkelsen
Copyleft Software AS


--
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: a feathiable solution displaying Windows program on Linux via ssh / X?

[Bobber Cheng]

Wine is a win32 emulator in Unix, *wine in cygwin* need to install lot 
of thing. The worst is that wine is currently under heavy development, 
many win32 apps could not run on it. e.g. IE.


VNC will share whole screen, i hope only app's wins would be shared. 
Although some version VNC(TightVNC <http://www.tightvnc.com/>) could 
share a window, but the result is pool. Unless some 
NX(http://www.nomachine.com/) cache tech integrate with VNC. it's not a 
consideration.


Michel Bardiaux wrote:


Bobber Cheng wrote:


Hi All,

I search the 
post(http://sourceware.org/ml/cygwin/2005-06/msg00627.html) at cygwin 
mailing list.


Had anyone found a feathiable solution displaying Windows program on 
Linux via ssh / X? If the answser is no, i beg X gurus to give me any 
advice how to implement it. Wine and VNC are not my choice.



You will have to explain what you exactly meant by 'wine' and 'vnc' 
and why you dont want them.


E.g. one possibility would be to run the windows app on a windows 
machine using *wine in cygwin*.




Bests,
Bobber Cheng







--
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: a feathiable solution displaying Windows program on Linux via ssh / X?

[Alexander Gottwald]

On Thu, 22 Sep 2005, Bobber Cheng wrote:

> Had anyone found a feathiable solution displaying Windows program on 
> Linux via ssh / X? If the answser is no, i beg X gurus to give me any 
> advice how to implement it. Wine and VNC are not my choice.

An alternative to Terminal client or cytrix is rdesktop. But besides that
there is no working solution to wrap windows programs with X11. You might
want to take a look at cygpeace which is not much more than a prove of 
concept which allowed to export winmine over x11.

http://www.freedesktop.org/~ago/cygpeace/

Before begging X gurus (which btw is the wrong group to ask) you should
check the win32-x11 archives http://sourceware.org/ml/win32-x11/ starting 
with July - September, 2002 until July - September, 2004. Some techniques 
for wrapping and redirecting windows GDI calls to X11 were discussed there
but most of the initial activity vaporized after few months.

Basicly there are a few ways which might work:

- build a display driver which uses X11 as backend
  x11_drv from wine might provide the conversion to X11 calls
- wrap GDI calls from applications with own, X11 aware implementations
  cygpeace aproach
- Check how Terminal Client works and implement a backend which uses X11 
  instead of RDP

bye
ago
BTW: Use rdesktop.
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

--
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: a feathiable solution displaying Windows program on Linux via ssh / X?

[Michel Bardiaux]

Bobber Cheng wrote:

Hi All,

I search the post(http://sourceware.org/ml/cygwin/2005-06/msg00627.html) 
at cygwin mailing list.


Had anyone found a feathiable solution displaying Windows program on 
Linux via ssh / X? If the answser is no, i beg X gurus to give me any 
advice how to implement it. Wine and VNC are not my choice.


You will have to explain what you exactly meant by 'wine' and 'vnc' and 
why you dont want them.


E.g. one possibility would be to run the windows app on a windows 
machine using *wine in cygwin*.




Bests,
Bobber Cheng




--
Michel Bardiaux
R&D Director
T +32 [0] 2 790 29 41
F +32 [0] 2 790 29 02
E mailto:[EMAIL PROTECTED]

Mediaxim NV/SA
Vorstlaan 191 Boulevard du Souverain
Brussel 1160 Bruxelles
http://www.mediaxim.com/

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

a feathiable solution displaying Windows program on Linux via ssh / X?

[Bobber Cheng]

Hi All,

I search the post(http://sourceware.org/ml/cygwin/2005-06/msg00627.html) 
at cygwin mailing list.


Had anyone found a feathiable solution displaying Windows program on 
Linux via ssh / X? If the answser is no, i beg X gurus to give me any 
advice how to implement it. Wine and VNC are not my choice.


Bests,
Bobber Cheng

--
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: invalid Window parameter error through ssh X forwarding

[Harold L Hunt II]

Replace 'ssh -X' with 'ssh -Y'.

Harold

Richard Gourdeau wrote:
I have just upgraded my xfree-cygwin setup (Xwin serv Release 4.3.0-64, 
etc.).

Some apps that worked through ssh without any problem with my previous 
setup (Xwin serv Release 4.3.0-58, etc.) are now exiting with errors 
messages related to an invalid Window parameter.

For example, in a xterm after an ssh connect with X forwarding, gftp 
starts but as soon as I try to select a menu item, I get the following 
error:
===
[EMAIL PROTECTED] gourdeau]$  gftp &
[1] 13684
[EMAIL PROTECTED] gourdeau]$ Gdk-ERROR **: BadWindow (invalid Window 
parameter)
  serial 3647 error_code 3 request_code 38 minor_code 0
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
  serial 3648 error_code 10 request_code 102 minor_code 0

[1]+  Exit 1  gftp
===
I have notice that the mouse cursor remains as an "X" and does not 
change to an arrow when moved over the "gftp" application.

I am using the "startxwin.sh" script from the distribution (unmodified) 
to start Xwin in multiwindow mode.

Should I specify some optional parameters or is this a known problem ?

invalid Window parameter error through ssh X forwarding

[Richard Gourdeau]

I have just upgraded my xfree-cygwin setup (Xwin serv Release 4.3.0-64, 
etc.).

Some apps that worked through ssh without any problem with my previous 
setup (Xwin serv Release 4.3.0-58, etc.) are now exiting with errors 
messages related to an invalid Window parameter.

For example, in a xterm after an ssh connect with X forwarding, gftp 
starts but as soon as I try to select a menu item, I get the following 
error:
===
[EMAIL PROTECTED] gourdeau]$  gftp &
[1] 13684
[EMAIL PROTECTED] gourdeau]$ Gdk-ERROR **: BadWindow (invalid Window 
parameter)
  serial 3647 error_code 3 request_code 38 minor_code 0
Gdk-ERROR **: BadAccess (attempt to access private resource denied)
  serial 3648 error_code 10 request_code 102 minor_code 0

[1]+  Exit 1  gftp
===
I have notice that the mouse cursor remains as an "X" and does not 
change to an arrow when moved over the "gftp" application.

I am using the "startxwin.sh" script from the distribution (unmodified) 
to start Xwin in multiwindow mode.

Should I specify some optional parameters or is this a known problem ?

--
Richard Gourdeau

Re: ssh/X with two hops

[Alexander Gottwald]

On Thu, 4 Sep 2003, Ehud Karni wrote:

> 1. It allows you to run anything on your office machine and see it on
>your home machine - not just X11 applications.
> 2. It is stateless - if the communication fails for any reason, you
>can reconnect and resume your work (like `screen' for ttys).
> 3. You have the options to connect "read only" and have multiple
>connections.
> 
> I know you can achieve 2 & 3 with Emacs on multiple X's too, but it is
> more complicated, and from my experience it fails more often.
> 

VNC is a good solution for non X11 apps. But with X11 apps you loose the 
advantage of local rendering of text. With VNC every drawing operation
is updated as bitmap which requires a fast connection.  

Point 2 is not achived easily with stock X11 software, so if the stateless
feature is required, then VNC is a good option.

The Read-only feature is a special, seldomly required feature.

The last two point do in my opinion not sum up to such a big advantage 
which would drive me to favor the slow bitmap transfers with VNC over
the slim X11 protocol.   

> You'll still need the ssh to securely connect and tunnel through your
> firewall, but you can disable the X11 forwarding (which is done on your
> gateway machine and is considered security breach by some).

VNC falls into the same "security breach" category as X11 Forwarding and
it is more likely the inexperienced users will setup an uncrypted VNC 
connection. X11 Forwarding is easyto use and always uses a secure channel.

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

Re: ssh/X with two hops

[Ehud Karni]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 3 Sep 2003 20:49:47 -0600, Robert Mecklenburg <[EMAIL PROTECTED]> wrote:
>
> AG> Most likely X11Forwarding is disabled on that host.
> AG>
> AG> check /etc/ssh/sshd_config for an entry
> AG> X11Forwarding yes
>
> That's it!  Works perfectly.  Thanks!

Although you solved your problem I propose to use VNC (GPLed, from
http://www.realvnc.org or one of its clones). It has several advantage
on running Emacs with X11 forwarding.

1. It allows you to run anything on your office machine and see it on
   your home machine - not just X11 applications.
2. It is stateless - if the communication fails for any reason, you
   can reconnect and resume your work (like `screen' for ttys).
3. You have the options to connect "read only" and have multiple
   connections.

I know you can achieve 2 & 3 with Emacs on multiple X's too, but it is
more complicated, and from my experience it fails more often.

You'll still need the ssh to securely connect and tunnel through your
firewall, but you can disable the X11 forwarding (which is done on your
gateway machine and is considered security breach by some).

Ehud.


- --
 Ehud Karni   Tel: +972-3-7966-561  /"\
 Mivtach - Simon  Fax: +972-3-7966-667  \ /  ASCII Ribbon Campaign
 Insurance agencies   (USA) voice mail and   X   Against   HTML   Mail
 http://www.mvs.co.il  FAX:  1-815-5509341  / \
 mailto:[EMAIL PROTECTED]  Better  Safe  Than  Sorry
-BEGIN PGP SIGNATURE-
Comment: use http://www.keyserver.net/ to get my key (and others)

iD8DBQE/V0UvLFvTvpjqOY0RAgOrAJkB5mErvrwkV7MiAGhQl4szyuGmcwCeNhtc
/WyXux+QvJ+5tESL9P13kU8=
=5lFV
-END PGP SIGNATURE-

Re: ssh/X with two hops

[Robert Mecklenburg]

AG> Most likely X11Forwarding is disabled on that host.
AG>
AG> check /etc/ssh/sshd_config for an entry 
AG> X11Forwarding yes

That's it!  Works perfectly.  Thanks!


TC> BTW - emacs works perfectly well over a terminal session.  No need
TC> for X at all.  You should be able to open a good-old MS-DOS
TC> prompt, telnet or ssh to your hearts content, then make sure
TC> TERM=vt100 on the remote system, then run emacs.

I haven't used emacs without X (by choice) since 1988! 8-)  Yes, it
works (pretty well) but why would I want a VW when I can have a BMW?
Seriously, thanks for your suggestion, I'm just trying to see how
close cygwin/xfree can get me to the Right Answer (tm).

Thanks,
-- 
Robert

Re: ssh/X with two hops

[Thomas Chadwick]

BTW - emacs works perfectly well over a terminal session.  No need for X at 
all.  You should be able to open a good-old MS-DOS prompt, telnet or ssh to 
your hearts content, then make sure TERM=vt100 on the remote system, then 
run emacs.

From: Robert Mecklenburg <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Cygwin XFree Users List <[EMAIL PROTECTED]>
Subject: ssh/X with two hops
Date: Wed, 3 Sep 2003 11:44:11 -0600
I'm a newbie at ssh and would like some advice.  I have a home pc
(windows xp) and an office pc (windows xp) behind a firewall/gateway
host (linux).  I want to run X at home and display (on my home X
server) an emacs running on my office pc.  Here is my most recent
attempt:
I have cygwin sshd running on my office machine...

1. startxwin.sh at home

2. In an xterm run "ssh -X -L 22:osaka:2200 gateway" this allows my to
   login directly to my office machine but leaves an unnecessary login
   on the gateway.  X port forwarding works in this login, but it is
   the wrong host.
3. In a new xterm run "ssh -X localhost".  Now I am logged onto my
   office machine and hopefully X ports are being forwarded, but no!
4. When I "echo $DISPLAY" on my office machine the variable is empty.

I have, of course, tried many other permutations of this procedure,
but this seems the closest to correct - but no joy.
Another permutation I've tried is to ssh to the gateway and then ssh
from the gateway to my office pc, but again the DISPLAY variable is
not set even though I use -X.
Any suggestions?

Thanks!
--
Robert
_
Get 10MB of e-mail storage! Sign up for Hotmail Extra Storage. 
http://join.msn.com/?PAGE=features/es

Re: ssh/X with two hops

[Alexander Gottwald]

On Wed, 3 Sep 2003, Robert Mecklenburg wrote:

> I'm a newbie at ssh and would like some advice.  I have a home pc
> (windows xp) and an office pc (windows xp) behind a firewall/gateway
> host (linux).  I want to run X at home and display (on my home X
> server) an emacs running on my office pc.  Here is my most recent
> attempt:
> 
> I have cygwin sshd running on my office machine...
> 
> 1. startxwin.sh at home
> 
> 2. In an xterm run "ssh -X -L 22:osaka:2200 gateway" this allows my to
>login directly to my office machine but leaves an unnecessary login
>on the gateway.  X port forwarding works in this login, but it is
>the wrong host.
> 
> 3. In a new xterm run "ssh -X localhost".  Now I am logged onto my
>office machine and hopefully X ports are being forwarded, but no!
> 
> 4. When I "echo $DISPLAY" on my office machine the variable is empty.

Most likely X11Forwarding is disabled on that host.

check /etc/ssh/sshd_config for an entry 
X11Forwarding yes

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

ssh/X with two hops

[Robert Mecklenburg]

I'm a newbie at ssh and would like some advice.  I have a home pc
(windows xp) and an office pc (windows xp) behind a firewall/gateway
host (linux).  I want to run X at home and display (on my home X
server) an emacs running on my office pc.  Here is my most recent
attempt:

I have cygwin sshd running on my office machine...

1. startxwin.sh at home

2. In an xterm run "ssh -X -L 22:osaka:2200 gateway" this allows my to
   login directly to my office machine but leaves an unnecessary login
   on the gateway.  X port forwarding works in this login, but it is
   the wrong host.

3. In a new xterm run "ssh -X localhost".  Now I am logged onto my
   office machine and hopefully X ports are being forwarded, but no!

4. When I "echo $DISPLAY" on my office machine the variable is empty.

I have, of course, tried many other permutations of this procedure,
but this seems the closest to correct - but no joy.

Another permutation I've tried is to ssh to the gateway and then ssh
from the gateway to my office pc, but again the DISPLAY variable is
not set even though I use -X.


Any suggestions?

Thanks!
-- 
Robert

Re: SSH X forwarding not working

[Chris Horn]

At 04:50 PM Thursday 3/6/2003, you wrote:
Hmm looked through the mail again and saw:

|> > ssh -x remote-host

Have you tried "ssh -X", capital X, using small x disables ssh
forwarding.
Sorry, sloppy typing.  I've been using -X, the text in this email was a typo.


Meanwhile:

/ Chris Horn <[EMAIL PROTECTED]> wrote:
| At the other end, /etc/ssh/sshd_config now has the line "X11Forwarding yes"
|
| Still no go.
|
| When I connect, the DISPLAY value on the remote box appears null.
| When I'm local, it's "localhost:0.0"
And this local, it is from the prompt you do ssh from?
Yeah.  When I'm in Cygwin XFree86 on my local machine in an xterm, I've 
been typing 'echo $DISPLAY' to see what it's set to.


| When I used xhost and set DISPLAY manually, things work:

just a note, you are aware that the X traffic goes unencrypted when
doing it this way (setting DISPLAY to host_done_ssh_from)?
Yes.  Which is why I want to get SSH's X forwarding working already!


| 2. on remote box set DISPLAY to "local_host:0.0"

Assuming local_host here is host_done_ssh_from?
Yeah.  I was on the remote machine (through a SSH session) and set DISPLAY 
to be the display of the machine I'm sitting at - which I've been calling 
local (because it's right in front of me).

Sorry, I guess I could've been clearer.


| Also, does anyone know how to cut and paste:
|  1. Within X (do I have to run XWin with -emulate3buttons?), and
If you have a threebutton mouse like microsoft with scrollball, you
probably can use the third button.. (like me)
Huh.  I think the problem is that I have the middle mouse button (the 
scrollwheel) set to double-click in Windows and that behavior is overriding 
what it would normally do in X - namely paste!

I exclusively run Linux on my personal machine at home, so not having paste 
is *really* frustrating!


|  2. between X and Windows?

There are work being done on this, check the mailinglist. xwinclip is
the keyword I think.
I'll check it out; thanks.

-
[EMAIL PROTECTED]
703.413.1100 x5100

Re: SSH X forwarding not working

[Chris Horn]

I had restarted sshd.

At 04:45 PM Thursday 3/6/2003, you wrote:
Chris,

Okay, so you had X11Forwarding disabled before.  What have you done to 
make sshd re-read its configuration file?  Specifically restarted 
sshd?  Restarted the entire machine?  What?  I suspect that sshd happily 
thinks that X11Forwarding is still disabled.

Harold

Chris Horn wrote:
At the other end, /etc/ssh/sshd_config now has the line "X11Forwarding yes"
Still no go.
When I connect, the DISPLAY value on the remote box appears null.
When I'm local, it's "localhost:0.0"
The error I receive when trying to run apps is "Gtk-WARNING **: cannot 
open display:"
When I used xhost and set DISPLAY manually, things work:
1. xhost +remote_host
2. on remote box set DISPLAY to "local_host:0.0"
3. run app, and it appears like it should!
Also, does anyone know how to cut and paste:
1. Within X (do I have to run XWin with -emulate3buttons?), and
2. between X and Windows?

Merci beaucoup.
chris.
At 04:02 PM Thursday 3/6/2003, you wrote:
viestissä torstai 6. maaliskuuta 2003 23:04, chris horn kirjoitti:

> greetings.  i've looked over the mailing list, but haven't been able to
> find out why using
> ssh -x remote-host

have you configured the remote end to accept x forwarding in
/etc/ssh/sshd_config?
--
/(anton)
-
[EMAIL PROTECTED]
703.413.1100 x5100


-
[EMAIL PROTECTED]
703.413.1100 x5100

Re: SSH X forwarding not working

[Andrew Markebo]

Hmm looked through the mail again and saw:

|> > ssh -x remote-host

Have you tried "ssh -X", capital X, using small x disables ssh
forwarding.

Meanwhile:

/ Chris Horn <[EMAIL PROTECTED]> wrote:
| At the other end, /etc/ssh/sshd_config now has the line "X11Forwarding yes"
|
| Still no go.
|
| When I connect, the DISPLAY value on the remote box appears null.
| When I'm local, it's "localhost:0.0"

And this local, it is from the prompt you do ssh from? 

| When I used xhost and set DISPLAY manually, things work:

just a note, you are aware that the X traffic goes unencrypted when
doing it this way (setting DISPLAY to host_done_ssh_from)? 

| 2. on remote box set DISPLAY to "local_host:0.0"

Assuming local_host here is host_done_ssh_from?

| Also, does anyone know how to cut and paste:
|  1. Within X (do I have to run XWin with -emulate3buttons?), and

If you have a threebutton mouse like microsoft with scrollball, you
probably can use the third button.. (like me)

|  2. between X and Windows?

There are work being done on this, check the mailinglist. xwinclip is
the keyword I think.

/Andy

-- 
 The eye of the beholder rests on the beauty!

Re: SSH X forwarding not working

[Harold L Hunt II]

Chris,

Okay, so you had X11Forwarding disabled before.  What have you done to 
make sshd re-read its configuration file?  Specifically restarted sshd? 
 Restarted the entire machine?  What?  I suspect that sshd happily 
thinks that X11Forwarding is still disabled.

Harold

Chris Horn wrote:
At the other end, /etc/ssh/sshd_config now has the line "X11Forwarding yes"

Still no go.

When I connect, the DISPLAY value on the remote box appears null.
When I'm local, it's "localhost:0.0"
The error I receive when trying to run apps is "Gtk-WARNING **: cannot 
open display:"

When I used xhost and set DISPLAY manually, things work:

1. xhost +remote_host
2. on remote box set DISPLAY to "local_host:0.0"
3. run app, and it appears like it should!
Also, does anyone know how to cut and paste:
1. Within X (do I have to run XWin with -emulate3buttons?), and
2. between X and Windows?
Merci beaucoup.
chris.
At 04:02 PM Thursday 3/6/2003, you wrote:

viestissä torstai 6. maaliskuuta 2003 23:04, chris horn kirjoitti:

> greetings.  i've looked over the mailing list, but haven't been able to
> find out why using
> ssh -x remote-host

have you configured the remote end to accept x forwarding in
/etc/ssh/sshd_config?
--
/(anton)


-
[EMAIL PROTECTED]
703.413.1100 x5100

Re: SSH X forwarding not working

[Chris Horn]

At the other end, /etc/ssh/sshd_config now has the line "X11Forwarding yes"

Still no go.

When I connect, the DISPLAY value on the remote box appears null.
When I'm local, it's "localhost:0.0"
The error I receive when trying to run apps is "Gtk-WARNING **: cannot open 
display:"

When I used xhost and set DISPLAY manually, things work:

1. xhost +remote_host
2. on remote box set DISPLAY to "local_host:0.0"
3. run app, and it appears like it should!
Also, does anyone know how to cut and paste:
1. Within X (do I have to run XWin with -emulate3buttons?), and
2. between X and Windows?
Merci beaucoup.
chris.
At 04:02 PM Thursday 3/6/2003, you wrote:
viestissä torstai 6. maaliskuuta 2003 23:04, chris horn kirjoitti:

> greetings.  i've looked over the mailing list, but haven't been able to
> find out why using
> ssh -x remote-host

have you configured the remote end to accept x forwarding in
/etc/ssh/sshd_config?
--
/(anton)


-
[EMAIL PROTECTED]
703.413.1100 x5100

Re: SSH X forwarding not working

[Andrew Markebo]

/ Chris Horn <[EMAIL PROTECTED]> wrote:
| Greetings.  I've looked over the mailing list, but haven't been able
| to find out why using
|
| ssh -X remote-host

Try to throw on one or two -v's to check what ssh thinks.

>From where do you do ssh -X remote-host, and what is the value of the
variable $DISPLAY at the prompt before ssh, and the prompt at the
other end when the ssh is connected.

What does the apps say in the other end when you try to start them?

  /Andy

-- 
 The eye of the beholder rests on the beauty!

Re: SSH X forwarding not working

[Anton Vaaranmaa]

Viestissä Torstai 6. Maaliskuuta 2003 23:04, Chris Horn kirjoitti:

> Greetings.  I've looked over the mailing list, but haven't been able to
> find out why using

> ssh -X remote-host

Have you configured the remote end to accept X forwarding in 
/etc/ssh/sshd_config?

-- 
/(anton)

SSH X forwarding not working

[Chris Horn]

Greetings.  I've looked over the mailing list, but haven't been able to 
find out why using

ssh -X remote-host

wouldn't actually let you run X apps on the distant machine (to display 
locally).  I'm using the absolute latest and greatest Cygwin XFree86 
(fetched yesterday).

Any help would be much appreciated.

NOTE: I use startx (I have also tried using xinit) and have added 'export 
DISPLAY=localhost:0.0' to my .xinitrc.

Thanks in advance.
chris.
-
[EMAIL PROTECTED]
703.413.1100 x5100

RE: ssh x forwarding

[Richard Campbell]

This probably should have been on the xfree list.

>From: Patrick Nelson [mailto:[EMAIL PROTECTED]]
>
>In ssh you get x forwarding.  But, I can't seem to get it working.  A
>command like:
>
>  ssh -l   
>
>always responds with something like:
>
> Gtk-WARNING **: cannot open display:
>
>Is there some configuration that needs to take place in cygwin first?  Yes
I
>can log in by dropping the  part and yes the  is available.
>Tried running the above from a terminal that displayed after doing a
>"startx" too... same result.  So I have to figure I just don't have
>something setup correctly.

At a minimum, you need to have the DISPLAY variable set before you 
execute the ssh, and you need to use the X forwarding (-X) option
to ssh

so:

export DISPLAY=localhost:0.0
ssh -X -l   

-Richard Campbell.

Re: Need help with ssh -X error message.

[Alexander Gottwald]

Booker wrote:

> Aloha,
> 
> When I connect to server using ssh -X ... I can log in fine, but when I
> log in an error message is displayed:
> 
> Warning: No xauth data; using fake authentication data for X11
^^
> forwarding.
> 
> but I continue with my log in and get into my shell.  I can run xclients
> fine and they tunnel back over the ssh connection.  But I am confused as
> to why I get that error message and everything still works.

It's not an error. It's a warning. By default the xserver is not setup to 
use the authentication cookies. ssh normally uses these cookies. But if none
is set, ssh will print this warning

bye
ago

NP: grauzone.02-12-23
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723

Need help with ssh -X error message.

[Booker]

Aloha,

When I connect to server using ssh -X ... I can log in fine, but when I
log in an error message is displayed:

Warning: No xauth data; using fake authentication data for X11
forwarding.

but I continue with my log in and get into my shell.  I can run xclients
fine and they tunnel back over the ssh connection.  But I am confused as
to why I get that error message and everything still works.

Booker

MELE KALIKIMAKA to everyone also!  http://64.224.244.55/

Re: Question of using ssh -X under cygwin-x86free

[Scott Alexander]

It can be either.  user or user@host i use

X -query -l  


- Original Message -
From: "Uwe Schmidtmann" <[EMAIL PROTECTED]>
To: "Paul Yeung" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 28, 2002 7:33 AM
Subject: Re: Question of using ssh -X under cygwin-x86free


> Hi.
>
> I am not absolutely sure, but isn´t it ssh -l user@host ???
>
> Regards,
>
> Uwe
>
> Paul Yeung wrote:
> > Hi,
> > ...
> > ssh -X -l username hostname
> > hostname's password:
> > Write failed: The descriptor is a file, not a socket
>
>
>

Re: Question of using ssh -X under cygwin-x86free

[Uwe Schmidtmann]

Hi.

I am not absolutely sure, but isn´t it ssh -l user@host ???

Regards,

Uwe

Paul Yeung wrote:
> Hi,
> ...
> ssh -X -l username hostname
> hostname's password:
> Write failed: The descriptor is a file, not a socket

RE: Question of using ssh -X under cygwin-x86free

[Harold Hunt]

Paul,

>From your example it looks like you literally entered 'username' and
'hostname' as the user's name and the host computer's name.  Did you really
do that?  If so, I would expect that you would get some sort of odd error.

Try using your real user name after the '-l' and the name of the host that
you want to connect to as the hostname.

Harold

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Yeung
> Sent: Tuesday, May 28, 2002 12:00 AM
> To: [EMAIL PROTECTED]
> Subject: Question of using ssh -X under cygwin-x86free
>
>
> Hi,
>
> I follow the instruction in the Cygwin/XFree86 User's Guide of installing
> the XFree86.
>
> When I used the "ssh -X" as described in the manual, I got the following
> error. Do you have any suggestion of what I have done wrong. I am running
> WinNt with service pack 6a on. I am using the latest version of
> Cygwin/XFree86 and the host is a Solaris 2.6 server.
>
> ssh -X -l username hostname
> hostname's password:
> Write failed: The descriptor is a file, not a socket
>
>
> Regards,
> Paul Yeung
>
>

Question of using ssh -X under cygwin-x86free

[Paul Yeung]

Hi,

I follow the instruction in the Cygwin/XFree86 User's Guide of installing
the XFree86.

When I used the "ssh -X" as described in the manual, I got the following
error. Do you have any suggestion of what I have done wrong. I am running
WinNt with service pack 6a on. I am using the latest version of
Cygwin/XFree86 and the host is a Solaris 2.6 server.

ssh -X -l username hostname
hostname's password:
Write failed: The descriptor is a file, not a socket


Regards,
Paul Yeung