Bug#908293: accountsservice: High CPU usage after system startup

[Francesco P. Lovergine]

On Tue, Oct 30, 2018 at 10:46:22PM -0400, Scott Bailey wrote:
>Package: accountsservice
>Version: 0.6.45-1
>Followup-For: Bug #908293
>
>Dear Maintainer,
>
>I noticed in passing that the accounts-daemon process is consuming 99%+ of
>one
>of my processors, on a long-term ongoing basis, and neither restarts (via
>systemctl) nor reboots seem to be curbing its enthusiasm.
>
>I'm responding to the original bug report, although that was for an earlier
>version, as the symptoms seem to largely mirror mine.
>
>Thanks,
>
>-Scott
>
>

Apparently, this also triggering autodir daemon that I use on our servers 
extensively since years. Recently, I had to install x2go/vnc and mate on 
several boxes to allow people to use a DE during covid‐19 lockdown here, and 
autodir randomly starts to log tons of messages such:

gen 29 09:21:31 YYYYY autodir[42811]: [autohome] warning: no user found with name XXXXXX.tiff
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] alert: module autohome failed on XXXXXX.tiff
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] warning: no user found with name XXXXXX.wbmp
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] alert: module autohome failed on XXXXXX.wbmp
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] warning: no user found with name XXXXXX.webp
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] alert: module autohome failed on XXXXXX.webp
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] warning: no user found with name XXXXXX.xbm
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] alert: module autohome failed on XXXXXX.xbm
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] warning: no user found with name XXXXXX.xpm
gen 29 09:21:31 YYYYY autodir[42811]: [autohome] alert: module autohome failed on XXXXXX.xpm

It seems directly due to the new services installed. XXXXX is generally an 
already logged user.
Of course that stops after restarting the autodir daemon, but high cpu times 
appear for accounts-daemon, systemd-logd (well, of course) and caja. I could 
probably mitigate the issue in autodir by stopping the continuous reporting, 
but there's something strange in the caja/accounts-daemon or both, not sure. 

The whole thing is quite annoying...


-- 
Francesco P. Lovergine