Hi, Description of problem: If the RHEL6 host that acts as the server for x2go has enabled polyinstantiated /tmp directories as per https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security-Enhanced_Linux/polyinstantiated-directories.html then x2go clients cannot connect. They fail with The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server. It seems that x2go needs the directory /tmp/.X11-unix/ to exist, be owned by root, and be mode 1777. Version-Release number of selected component (if applicable): x2goserver-4.0.1.13-4.el6.x86_64 RHEL 6.5 How reproducible: 100%. Steps to Reproduce: 1. Uncomment the line in /etc/security/namespace.conf that reads: #/tmp /tmp-inst/ level root,adm 2. Try to log in to that host via x2goclient. Actual results: x2go fails. Expected results: x2go works. Additional info: A workaround is to add something like the following to the end of /etc/security/namespace.init: if [ "$1" = "/tmp" ]; then XSOCKDIR=/tmp/.X11-unix if [ ! -d $XSOCKDIR ]; then mkdir $XSOCKDIR chmod 1777 $XSOCKDIR fi fi It would be great if x2go could fix this itself though. Ideally it would either not need /tmp/.X11-unix, or be able to create it itself when needed. Thanks.
Passed on to upstream for now. Will try to take a look at it sometime if they don't get to it first.
Please test the builds from here: http://koji.fedoraproject.org/koji/taskinfo?taskID=7069091 Hopefully it will fix both of these issues.
> http://koji.fedoraproject.org/koji/taskinfo?taskID=7069091 Seems to work for me. Thanks!
*** Bug 1101726 has been marked as a duplicate of this bug. ***
I believe upstream will be releasing a new version shortly. Will push that when released.
nx-libs-3.5.0.27-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/nx-libs-3.5.0.27-1.el6
nx-libs-3.5.0.27-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.