I've discovered a hackish workaround that may be helpful for someone to
know about. If I use 'sudo caja' then it displays as expected. Running
caja as non-root user still spawns a window on the remote machine, just
like for everyone else.
$ ssh -X user@IP
Welcome to Ubuntu
$ export XAUTHORITY=$HOME/.Xauthority (needed to use sudo)
$ sudo caja
TERMINAL OUTPUT
(caja:4273): dbind-WARNING **: 20:17:39.773: Couldn't connect to accessibility
bus: Failed to connect to socket /tmp/dbus-DgQ4NgfGBw: Connection refused
Initializing caja-open-terminal extension
RuntimeError: object at 0x7fdfe93a75c0 of type FolderColorMenu is not
initialized
RuntimeError: object at 0x7fdfe960d300 of type RenameMenu is not initialized
Then caja forwards as expected from file-server to local workstation
over ssh. But now you are user:root and modifying other users files can
result in undesired permission changes so use with care.
Can still use Thunar or Dolphin or whatever alternate file-manager...but
we shouldn't have to! I still run x1 gnome2 desktop and simply never
have/had this problem when caja was nautilus so it's likely something
simple introduced EARLY in MATE. Please guys, fix this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1815318
Title:
mate 18.04.1 xserver won't open caja on local machine
Status in MATE Desktop:
New
Status in caja package in Ubuntu:
Confirmed
Status in openssh package in Ubuntu:
Invalid
Bug description:
Steps to reproduce:
1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e.
192.168.1.162)
2. Install SSH server on Ubuntu MATE 18.04 LTS
3. Open terminal on other remote system (client) and execute command to run
Caja over X forwarding:
ssh -X user@192.168.1.162 caja
Expected results:
* Caja is shown on remote (client) screen with window title *folder (on
hostname)*
Actual results:
* Caja is not shown on remote (client) screen, but launches on server locally.
Note: this works normally if server runs Ubuntu MATE 16.04 LTS, but
fails with 18.04 LTS.
---
Original description below:
I can open a remote terminal using ssh -X 192.168.1.162. All other
gui's that I've tested opened locally except the file manager Caja.
When issuing caja in the remote terminal, I get nothing locally. Caja
does open on the remote machine however, just not locally. The ssh -X
18.04.1 client still works connecting to a mate 16.04 server. I've
tested this on numerous mate 18.04 clients, two 16.04 servers and two
18.04 servers, all mate. Something is wonky with caja on an 18.04.1
server.
Please let me know if I can provide any more information. The only
file manager I've tested that works is an X file manager, xfimage.
X2go works and connects to servers, SSH Connect to Server works, why
isn't the remote X terminal working using caja?
To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1815318/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
