Dear Maintainer,

I have used Debian Wheezy on my laptop for several years, and at some point
of time I noticed freezes in lightdm's login screen. Further investigatio with
htop showed, that the accounts-daemon uses almost 100% of CPU time on one of
cores.

Sending the KILL signal to the accounts-daemon instantly releases the freeze
of lightdm, but login attempt in lightdm restarts the accounts-daemon, which
starts to consume 100% of CPU time on one core again and after that I have
another freeze in lihtdm. Killing the accounts-daemon the second time helps
to successfully login.

Also, the accounts-daemon may stop its strange behaviour by itself after
some rather long period of time. There was a single time when I noticed that
it was gradually allocating more and more memory, but this particular
behaviour was not noticed ever again.

For now I run this bash one-line script as a quick and dirty fix:

# while : ; do pkill -KILL accounts-daemon ; sleep 3 ; done

I have included a compressed strace log of the accounts-daemon process,
captured while it was behaving strange.

I understand, that Debian Wheezy is now on LTS, but I have not found any signs
at bugs.freedesktop.org that something like that was ever reported and fixed.
I will live everything on my laptop intact for some time to provide additional
information if it is neded.

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,

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

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