[Bug 239395] can't start forwarded X11 consolehelper apps on remote SSH server

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=239395


Nik Lam <nik at med.usyd.edu.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nik at med.usyd.edu.au
               Flag|needinfo?(Triv at aol.com)     |




--- Comment #17 from Nik Lam <nik at med.usyd.edu.au>  2009-04-25 11:19:24 EDT ---
Hi,

I'm now noticing this problem on Fedora 10 x86_64 too. I used to be able to
successefully run 

 sudo virt-manager

on a Centos 5 box with X forwarding activated and the virt-manager gui would
display locally.

I haven't done it in a while and both operating systems have had packages
updated several times since I last successfully ran it, so I'm not sure when
the change occurred which is causing the problem. Other that package updates,
nothing that I can think of on either the ssh server or client has been
modified.

N.B. I'm running sshd on a non-standard port.

Here's an example of the ssh session:

[lnik at fedora10 ~]$ ssh -X -p 3923 centos5.example.com
lnik at centos5.example.com's password: 
Last login: Sun Apr 26 01:06:21 2009 from example123.dyn.example.com
###########################################################################
# Centos5
#
###########################################################################
/usr/bin/xauth:  creating new authority file /home/lnik/.Xauthority
[lnik at centos5 ~]$ sudo virt-manager 
X11 connection rejected because of wrong authentication.
The application 'virt-manager.py' lost its connection to the display
localhost:10.0;
most likely the X server was shut down or you killed/destroyed
the application.
[lnik at centos5 ~]$

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.