Thursday, March 06, 2008

Gdk-WARNING **: Connection to display localhost:10.0 appears to be untrusted

Have you ever had problems running X applications over ssh that did not involve issues with xauth. Here is a tip I found after getting error like this:
Connection to display localhost:10.0 appears to be untrusted. Pointer and keyboard grabs and inter-client communication may not work as expected.
or
Warning: untrusted X11 forwarding setup failed: xauth key data not generated
So, instead of simply using "ssh -X user@host", try using "ssh -2 -C -Y user@host" instead.

-2 Forces ssh to try protocol version 2 only.
-C Requests compression of all data ... which can be desirable in low bandwidth situations.
-Y Enables trusted X11 forwarding.

Using -Y is what got rid of the warning and subsequent functionality issue with the X application. But the compression helped speed things up quite a bit also.

Even with these new command line parameters I still get the warning:
Warning: No xauth data; using fake authentication data for X11 forwarding.
Anyone know what the issue there is?

Anyway, I hope that helps you as much as it did me.

11 comments:

Vernon D said...

Thanks for the update. I've been wondering about how to resolve that problem.
Dad
lol

Anonymous said...

Thanks, Vernon. I just started using Puppy 4.1 on my laptop to SSH to my Puppy 3.01 desktop at home. I had no difficulty using 3.01 on my laptop, and initially thought it was a Gtk problem.

I found that I needed only the -Y option, but the compression is welcome also.

Spanky

Dru Jensen said...

Thanks for the post!

eivindgl said...

Thanks, amazing, everything is much more responsive now. ..

Anonymous said...

Fantastic! This worked perfectly for me and resolved my lag issue as well.

Paul said...

Thanks for advice,
it works
still I see the same message " No xauth data; using fake authentication data"
I'm waiting for your solution:)

Scott Heaberlin said...

Thanks for this!

Even on an intranet the -C sped up X11 forwarding tremendously for me; even cleared up some odd window rendering behavior (huge space between gnome menu and window content area, etc) on my mac client to ubuntu server setup.

Anonymous said...

Thanks, this solved a BadAtom problem with remotely started firefox.

Naff said...

Thanks dude, made working from home a lot more comfortable. Emacs doesn't crash on me any more. woooo!

Anonymous said...

Thanks for sharing dude. I was having a problem loading wireshark, it was taking too long to load the dissectors. Your tip snapped it up.

Anonymous said...

Thanks!!! That was exactly my problem. Wonder why it happens to begin with, as ssh -X works fine usually...