schroot and click-chroot-agent are not closed when exiting qtcreator

[Didier Roche-Tolomelli]

click-chroot-agent is still running after qtcreator is closed. As a consequence, as it's only SIGTERM (and then SIGKILL if taking too long) on session closing, it doesn't teardown the schroot on the system.

This schroot is of course restored after reboot, even if the user doesn't use qtcreator.

I think this is what should happen:
- when qtcreator is exiting, a signal to click-chroot-agent should be send to terminate
- when click-chroot-agent is receiving a terminate signal, it should teardown all the schroot that it's tracking.

[Benjamin Zeller (zeller-benjamin)]

Disagree, the agent should not tear down the session when QtC is closed. It should tear down when you logout of the session. Its absolutely possible there are multiple QtC instances are running.

Can you check if its tearing down if you logout from your user session?

[Didier Roche-Tolomelli (didrocks)]

After testing, it indeed closes the schroot session on session shutdown, but not on system shutdown

[Didier Roche-Tolomelli (didrocks)]

For the record, the behavior is quite flaky as we saw. We discussed about it, and I propose to provide a systemd job at least to force tearing down ubuntu-sdk schroot sessions on reboot. I'll work on this