We shouldn't allow to shutdown the system when a installation or a update is in progress

[Raphael Isemann]

The system shouldn't allow to abort things such as:

* apt-get upgrade
* update manager installing updates
* software center installation

as that could result in a inconsistent system that needs manual intervention to fix in most cases (e.g. apt-get install -f).

It seems that checking if dpkg is locked is a good way to determine if it is safe to shutdown (if i understood that correctly from shnatsels explanation).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Anderson Lorencini (lorencini-brdev)]

That really is a problem. How should we handle it? By showing the user a message, and giving him the option to shutdown anyways? By installing the updates and only then shutdown, windows style? Or by forbidding the shutdown completely? Personally, i think the second option is the best. Because, that way, i can order it to shutdown, and just leave it there, knowing that when i get back home, for example, it will be off.

[notreallyhere (notreallyhere-deactivatedaccount)]

In my opinion the best option is to tell the user about on going update/whatever and inform system will be halted when done.

[Cameron Norman (cameronnemo)]

So getting a systemd-inhibit (works on all logind systems) delay lock on the shutdown action seems to be a good way to do this, no?

[Cameron Norman (cameronnemo)]

http://www.freedesktop.org/wiki/Software/systemd/inhibit/

[Sergey "Shnatsel" Davidoff (shnatsel)]

This is already implemented for unattended-upgrades, i.e. when security updates are installed automatically in the background. It should be fairly trivial to adapt that check to handle user-initiated upgrades as well.