Red Hat Bugzilla – Bug 146061
Remote gnome-terminal through ssh tunnel fails
Last modified: 2007-11-30 17:10:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5)
Description of problem:
Whenever I try to use ssh (or any other remote X method for that
matter) to start up a gnome-terminal (or several other gnome programs)
it always fails with a BadAtom error.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.ssh -X <some host> gnome-terminal
The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
(Details: serial 67 error_code 5 request_code 20 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()
Expected Results: I expect a nice gnome-terminal running on the
remote host to appear on my screen.
ssh -X seems to work for 'dia'. 'gimp' made it through the 'upgrade
from 2.0 to 2.2' dialog, and now it consistently crashes.
What happens if you use ssh -Y instead of ssh -X?
*** This bug has been marked as a duplicate of 134425 ***
Can you point me at any good documentation describing the exact
difference between -X and -Y? I'm just curious.
-X means that ssh will use untrusted auth cookies for it's connections
to the xserver.
-Y means that ssh will use trusted auth cookies.
The xauth man page describes this:
If the trusted option is used, clients that connect
using this authorization will have full run of the display, as usual.
If untrusted is used, clients that connect using this authorization
will be considered untrusted and prevented from stealing
or tampering with data belonging to trusted clients. See the
SECURITY extension specification for full details on
the restrictions imposed on untrusted clients. The
default is untrusted.
If you have the package xorg-x11-doc installed, then you can find the
SECURITY extension specification in
Thanks a whole bunch. I spent about an hour googling last night and
while I was able to find the -Y option, I couldn't find any
explanations of what it did, just vague hints.
I'm going to add this to the main report so people who are hunting for
it are more likely to find the explanation.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.