Shutdown takes a long time; cerbere vs systemd

[quequotion]

I think cerbere is fighting with systemd during shutdown.

I had set org.pantheon.desktop.cerbere.crash-time-interval to 10,000 while working on some indicators (broken indicators can cause continuous crashing of wingpanel) and lately it's taking a long time, almost a minute, to shut down.

See attached shutdown log.

I think the problem would be the same with the default timeout, although it would happen faster. It looks like cerbere thinks systemd killing the desktop is a crash--or perhaps systemd's method does not allow the processes to exit cleanly?

One way to avoid this would be to somehow ensure cerbere is killed before the desktop on shutdown, which I would figure gnome-session does anyway but that doesn't seem to be what's happening (not sure if gnome-session is properly told to exit before systemd starts killing stuff).

[quequotion (quequotion)]

How do cerbere, plank, and wingpanel handle SIGHUP?
https://bbs.archlinux.org/viewtopic.php?pid=1617469#p1617469

There's ongoing discussion of systemd's decision to send both SIGHUP and SIGTERM on their github as well:
https://github.com/systemd/systemd/issues/1615

[quequotion (quequotion)]

Workaround from that github discussion:

# echo kernel.core_pattern=core > /etc/sysctl.d/50-coredump.conf

https://github.com/systemd/systemd/issues/1615#issuecomment-203507283

[quequotion (quequotion)]

Note that above workaround will start dumping cores (core.$pid) into ~/

Unfortunately it seems like any deviation from kernel.core_patter=core, even to put them in another directory, brings back the delayed shutdown.