Source: caja Severity: important 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). -- Francesco P. Lovergine
