FYI: ssh X forward behavior

[Warren Togami <wtogami redhat com>]

On Fri, 23 Jul 2004, Luke Schierer wrote:
> ----- Forwarded message from Warren Togami <wtogami redhat com> -----
>
> [warren metzingen warren]$ 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 207 error_code 3 request_code 2 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.)
>
> Any ideas?

From: Etan Reisner
ssh changed some of it's options "recently" so that -X no longer
forwards X the way it used to. ssh -X forwards in some sort of 'safe'
mode which doesn't allow apps to do certain things they might want to
do. Try ssh -Y which "[e]nables trusted X11 forwarding" according to the
manpage.


The man page of ssh says to be cautious of the -X option, and does not 
mention any caution next to the -Y option.  Perhaps that could use some 
clarification upstream, and we should mention this change of behavior in 
FC's release notes?

Warren Togami
wtogami redhat com