nigra truo | 18 Jan 20:57 2013
Picon

follow up: connection failed xhost: unable to open display (again)

Hi,


following up on the subject, I found out some more things:

quote:
I also noticed that it works for user Z, I can open a session. But
currently never for user Y.

It really does not work for this user and I don't understand why. I have enough space on the filesystem, I erased the .x2go directories in user Ys home folder. I can login over ssh with Y, so that is not a problem.
This problem by the way started happening after a I had a power failure on my server, so I wonder if something got corrupted. I reinstalled (purged) x2goserver, so the x2go install should be fine. 

I now receive the xhost unable to open display on any system I try it with, with different OSes.


When connecting from Windows 7 to user Z, I can establish a X2go session and when I use the Client app via gui, it fails to connect to user Y, BUT if I run it in the CLI, it works:

mm <at> myserver:~$ x2goclient-cli --user Y --server localhost
Password:
xhost:  unable to open display ""
xhost:  unable to open display ""
ln: creating symbolic link `/tmp/.x2go-Y/session-C-Y-52-1358533596.log': File exists
xhost:  unable to open display ""


So these xhost error messages are coming from the x2goserver and only for that one user (which is the strangest thing)

So far I have not been able to enable debugging logging in x2goserver, editing the config file and restarting the server. The x2goserver does totally minimal logging and does not show what is wrong and why I cannot establish the connection. 


I have had lots and lots of trouble with xhost errors in the past, on any Linux box and the documentation that exists on it is totally shady and unconclusive. X seems to have a very weird idea of what security means and how it is instituted. (at where root is not allowed to access a users desktop without prior having given permission to it)

There must be something special about user Y, something that x2go saved in the home dir. What directories would I have to clean up to erase all cache / config files that x2go might store there when an external client connects to it?

Any pointers would be welcome. 

Thanks,

Markus
<div>
<p>Hi,</p>
<div><br></div>
<div>following up on the subject, I found out some more things:</div>
<div><br></div>
<div>quote:</div>
<div>
<span>I also noticed that it works for user Z, I can open a session. But</span><br><span>currently never for user Y.</span>
</div>
<div><br></div>
<div>It really does not work for this user and I don't understand why. I have enough space on the filesystem, I erased the .x2go directories in user Ys home folder. I can login over ssh with Y, so that is not a problem.</div>
<div>This problem by the way started happening after a I had a power failure on my server, so I wonder if something got corrupted. I reinstalled (purged) x2goserver, so the x2go install should be fine.&nbsp;</div>
<div><br></div>
<div>I now receive the xhost unable to open display on any system I try it with, with different OSes.</div>
<div><br></div>
<div><br></div>
<div>When connecting from Windows 7 to user Z, I can establish a X2go session and when I use the Client app via gui, it fails to connect to user Y, BUT if I run it in the CLI, it works:</div>
<div><br></div>
<div>
<span>mm <at> myserver:~$ x2goclient-cli --user Y --server localhost</span><br><span>Password:</span><br><span>xhost: &nbsp;unable to open display ""</span><br><span>xhost: &nbsp;unable to open display ""</span><br><span>ln: creating symbolic link `/tmp/.x2go-Y/session-C-Y-52-1358533596.log': File exists</span><br><span>xhost: &nbsp;unable to open display ""</span>
</div>
<div><br></div>
<div><br></div>
<div>So these xhost error messages are coming from the x2goserver and only for that one user (which is the strangest thing)</div>
<div><br></div>
<div>So far I have not been able to enable debugging logging in x2goserver, editing the config file and restarting the server. The x2goserver does totally minimal logging and does not show what is wrong and why I cannot establish the connection.&nbsp;</div>
<div><br></div>
<div><br></div>
<div>I have had lots and lots of trouble with xhost errors in the past, on any Linux box and the documentation that exists on it is totally shady and unconclusive. X seems to have a very weird idea of what security means and how it is instituted. (at where root is not allowed to access a users desktop without prior having given permission to it)</div>
<div><br></div>
<div>There must be something special about user Y, something that x2go saved in the home dir. What directories would I have to clean up to erase all cache / config files that x2go might store there when an external client connects to it?</div>
<div><br></div>
<div>Any pointers would be welcome.&nbsp;</div>
<div><br></div>
<div>Thanks,</div>
<div><br></div>
<div>Markus</div>
</div>

Gmane