In UM 16.04 (and 16.10, 17.04 and 17.10) I could get the remote machine's files GUI just by using the ssh -X [email protected] command and then issuing the caja command.
Caja does indeed open and display on the server but not on my local machine. Does anyone know why this happens or more importantly how I can get a remote GUI to display on my local machine?
X2go works as it always has, more or less perfectly and SSHFS is flawless. Only X forwarding seems broken.
I tried installing and then using XPRA on both client and server machines but neither worked - I could see caja opening on the server across the room but it didn’t open locally (on the client). Probably bug reporting time…
Edit: I installed gksu and its’ supporting library on two servers and then I could get a local GUI by issuing sudo caja using the X client. The problem has to do with the X server, not the client.
Yes, I’ve tried pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY caja on every ssh connection and it doesn’t appear to work.
Just a while ago, after ssh -X into a server, I entered pluma /home/michael/Documents/special.txt and pluma opened the requested document on the server.
This has something to do with caja, my favorite file manager. Essentially, I’m here (using MATE) because of caja. caja /home/data3/ doesn’t work either.
Over on ubuntuforums, Morbius1 came up with a pretty good workaround though not a solution, sudo -E caja which worked to open an administrative remote Caja locally. I’ve been able to uninstall the gksu .debs that I’ve been using. Great!
By the way, if you use sudo on gui apps, any configuration file written to home directory will be owned by root. In case caja writes a configuration file to home dir. That's something you probably don't want to do. That's why gksudo was used.
