Remote Log in Machine with X via SSH

[notroot]

Hello all. So, we have this machine sitting in a back room for people to log into and use. We want people to be able to run programs graphically with X Forwarding via SSH. So, we installed all the libraries, turned on X Forwarding and it works, more or less.

Windows launched seem to crash all the time on us. Like this.

Code: Select all

checkers [~] > gaim
The program 'gaim' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2219 error_code 3 request_code 38 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

or

Code: Select all

checkers [~] > emacs
X protocol error: BadWindow (invalid Window parameter) on protocol request 38

These errors are pretty easy to re-create usually by attempting to highlight text, or clicking on a menu, or something.

I had the same problem with a Gentoo workstation box of mine. Also, it doesn't seem to matter what the client is running, we have tested it on OS X, Ubuntu, Solaris, and Gentoo. Alright, any ideas?

[ticapix]

Hi

man ssh

or ssh -Y

Pierre

[notroot]

Ok, I would have never thought that it was a trusted networks issue.

So, the next question is, is there a way to configure it on the server side so that the users don't have to have the -Y option? You will have to understand that out users are quite dumb and rather annoying.

[davidblewett]

Take a look at using NX:
http://www.nomachine.com

It will help save a lot of network bandwidth, and should be easier to administer. There are ebuilds for the commercial as well as free implementation.