I believe this is just a different behavior in caja itself. You see, in
both cases there is already a caja process running. In bionic's version,
if you run caja again, it doesn't bring up a new copy, but instead uses
the existing one to spawn the new windows:

ubuntu@bionic-mate:~$ ps fxaw|grep caja|grep -v grep
10308 ?        Sl     0:01          \_ caja
ubuntu@bionic-mate:~$ caja
ubuntu@bionic-mate:~$ ps fxaw|grep caja|grep -v grep
10308 ?        Sl     0:01          \_ caja
ubuntu@bionic-mate:~$ caja
ubuntu@bionic-mate:~$ ps fxaw|grep caja|grep -v grep
10308 ?        Sl     0:01          \_ caja

But I have many new windows opened already.

In xenial, I do get new processes:
ubuntu@xenial-mate:~$ caja &
[1] 2764
ubuntu@xenial-mate:~$ Initializing caja-open-terminal extension
/usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You 
have imported the Gtk 2.0 module.  Because Gtk 2.0 was not designed for use 
with introspection some of the interfaces and API will fail.  As such this is 
not supported by the pygobject development team and we encourage you to port 
your app to Gtk 3 or greater. PyGTK is the recomended python module to use with 
Gtk 2.0
  warnings.warn(warn_msg, RuntimeWarning)
sys:1: PyGIWarning: Caja was imported without specifying a version first. Use 
gi.require_version('Caja', '2.0') before import to ensure that the right 
version gets loaded.
Initializing caja-main-menu extension
** Message: Initializing gksu extension...
ps fxaw|grep caja|grep -v grep
 2764 pts/8    Sl     0:00              \_ caja
 2338 ?        Sl     0:00          \_ caja

This is definitely not a problem with openssh, and one could argue caja is 
behaving like intended, but I'll leave that for others to decide. Marking the 
openssh task as invalid.

** Changed in: openssh (Ubuntu)
       Status: New => Invalid

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.

  mate 18.04.1 xserver won't open caja on local machine

Status in ubuntu-mate:
Status in caja package in Ubuntu:
Status in openssh package in Ubuntu:

Bug description:
  Steps to reproduce:
  1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e.
  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@ caja

  Expected results:
  * Caja is shown on remote (client) screen with window title *folder (on 

  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 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

  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:

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

Reply via email to