Due to smart working increase, I recently installed mate for our users at job, with
x2go/vnc servers. Soon, I found that caja randomly starts to cause high cpu loads,
and having autodir even installed it also started to log tons of messages
like:

/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] warning: no user found with name <username>.bmp
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] alert: module autohome failed on <username>.bmp
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] warning: no user found with name <username>.cur
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] alert: module autohome failed on <username>.cur
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] warning: no user found with name <username>.gif
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] alert: module autohome failed on <username>.gif
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] warning: no user found with name <username>.icns
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] alert: module autohome failed on <username>.icns
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] warning: no user found with name <username>.ico
/var/log/syslog.1:Feb 24 18:31:07 milos autodir[3794]: [autohome] alert: module autohome failed on <username>.ico

[...]

where <username> is a valid user id.

This eventually causes big issues for dozens of GBs of similar messages in a few days. Of course, a workaround
for the syslog stress is rate-limiting the autodir process in rsyslog configuration, but the reason for
the apparent looping of caja is unknown. Even, that starts randomly, probably
triggered by unknown interactions of the user with caja. This is specific of the
mate desktop, never saw with other environments (even if here we are not big
GUI users, and often use lighter WMs).

Dear Maintainer,

Hi,

I believe I'm experiencing the same issue. If not, the symptoms are
similar. I run Debian 11 with MATE as desktop environment. Every time I
log into my user the process below is the highest CPU consumming
process and the average load of the PC sits at around 30%, no other
programs initiated.

/usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -
nolisten tcp vt7 -novtswitch

The following step make htop to be the most demanding process with the
average load of the PC sitting at around 0.5%. Which is the situation I
would expect when no other program is running.

Below are the caja processes I see when I first log in. Killing that
process PID 1455 listed below solves the issue. I've reproduced this
several times. Killing the one with "--no-default-window" one made the
trick every time.

```
$ ps -ef | grep caja
rock        1455    1195  2 18:09 ?        00:00:01 /usr/bin/caja --no-
default-window
rock        9195    1224  0 18:10 ?        00:00:00 /usr/bin/caja
rock        9197    7059  0 18:10 pts/1    00:00:00 grep --color=auto
caja
```

Hope this helps someone narrow down the issue.

Please let me know if there's anything else I could do to debug this
further.