Bug#890833: Intermittent 90s shutdown delay: at-spi-dbus-bus.service: State 'stop-sigterm' timed out

[Simon McVittie]

Control: retitle -1 Intermittent 90s shutdown delay: at-spi-dbus-bus.service: State 'stop-sigterm' timed out
Control: reassign -1 at-spi2-core 2.22.0-6+deb9u1

On Mon, 26 Feb 2018 at 04:51:43 +0300, Sergey Antonov wrote:
> Hi. I have same problem with AT SPI...
> 
> lut 06 14:30:47 B2-46-AA-2018 systemd[612]: at-spi-dbus-bus.service: State 'stop-sigterm' timed out. Killing.
> lut 06 14:30:47 B2-46-AA-2018 systemd[613]: pam_unix(systemd-user:session): session closed for user Debian-gdm
> lut 06 14:30:47 B2-46-AA-2018 systemd[612]: at-spi-dbus-bus.service: Killing process 648 (at-spi-bus-laun) with signal SIGKILL.

The per-user instance of systemd sends SIGTERM to at-spi-dbus-bus.service
(at-spi-bus-launcher). If the processes in that service still haven't
exited 90 seconds later, systemd logs this message and follows up
with SIGKILL. That means at-spi-bus-launcher isn't exiting promptly,
which seems like a bug in at-spi-bus-launcher.

These log messages aren't seen in all cases, but that might just mean
that the system instance of systemd is killing the per-user instance
before it can log them. You could test this theory by reducing the timeout
used by the per-user instance, by configuring /etc/systemd/user.conf like
this:

    [Manager]
    DefaultTimeoutStopSec=60s

If my theory is correct, then that will reduce your shutdown delay from
90 to 60 seconds on the occasions when shutdown is delayed, and result in
those messages being logged every time.

    smcv