https://bugzilla.novell.com/show_bug.cgi?id=663407
https://bugzilla.novell.com/show_bug.cgi?id=663407#c31
--- Comment #31 from Egbert Eich 2012-03-23 16:08:23 UTC ---
I'm just looking into your issue.
This:
beholder:~$ xeyes
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyError: Can't open display:
localhost:10.0
seems to come from the server side, ie wrong authentication between sshd and
Xserver.
In:
glum:~$ ssh -X beholder
Warning: No xauth data; using fake authentication data for X11 forwarding.
/usr/bin/xauth: file /home/msvec/.Xauthority does not exist
the last line is generated when /home/msvec/.Xauthority on beholder does not
exist. This does not really matter as sshd creates one for you.
The line in the middle (Warning: ...) looks fishy: this line is generated when
ssh doesn't find an entry in the local $XAUTHORITY file which should be
generated by your display manager and will remain valid for the lifetime of
your session.
So the reason why this happens is on 'glum': what ssh does, is to fork and
execve /usr/bin/xauth with the command line argument "list $DISPLAY".
* What does "/usr/bin/xauth list $DISPLAY" return? I bet nothing.
* What do you get when you do "echo $DISPLAY"?
This issue may be related how you set your $DISPLAY variable on your system (ie
glum). It seems that this is set so that xauth cannot match anything.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.