Software installation or update doesn't block session exit

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

Since this bug has a nicer summary I marked the old bug as a duplicate of this one. Thanks.

Actually unity should check the ActiveTransactions property of aptdaemon before shutting down, since the transaction can continue even if the client is arround anymore.

I closed the bug for aptdaemon since the infrastructure should be already available.

I just discussed this with Michael. I may have messed up the details, but here's what I understand.

There are many different kinds of tasks for which you should be prompted to wait before a logout goes ahead. This already happens when you have an unsaved document in a well-behaved application (like GEdit or LibreOffice). Other examples include burning a CD, syncing an audio player, defragmenting a disk, or sculpting something with a 3D printer.

It shouldn't be Unity's job to detect all of these. It shouldn't be Unity's job even to know about any of them in particular; that wouldn't scale. That's why there's a gnome-session API for individual applications to announce that now would not be a good time to log out ... not yet ... not yet ... okay, now's good. http://live.gnome.org/SessionManagement/GnomeSession#A8._QueryEndSession

However, for package installation and removal, it's not so simple. As you point out, Sebastian, Ubuntu Software Center may not be running any more while an installation or removal completes. But beyond that, aptdaemon is running on the system bus, not the session bus. This has the advantage that you don't even need to be logged in *at all* for a task to complete. But it has two disadvantages. First, if a Debconf question occurs, there's no-one to answer it. And second, there is, apparently, no system-level equivalent to the gnome-session API for aptdaemon to inhibit shutdown -- so the machine just shuts down and leaves us with this corrupt package state.

So unless a system-level shutdown inhibit API is implemented, there are two ways to prevent the corruption problem here.
(1) In the short term, inhibit logout when there are any tasks. Michael says update-notifier is an appropriate place to do this, so I'm moving this report there.
(2) In the long term, add a check to the shutdown script so that it waits until all tasks are completed. I'm skeptical about how good this would look (and what happens if a maintainer script hangs?), but we can consider that in more detail later.

Systemd's logind introduced a new DBus interface to inhibit shutdown or suspend.

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

We would need support in unity.

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

<seb128> http://www.freedesktop.org/wiki/Software/systemd/inhibit/
<seb128> "shutdown inhibits high-level system power-off and reboot requested by (unprivileged) users"
<seb128> that's part of logind
<seb128> (e.g it's already being used, not part of changing pid 1)
<seb128> like that page has an example of pseudo code
<seb128> "fd = Inhibit("shutdown:idle", "Package Manager", "Upgrade in progress...", "block");"
<seb128> that's basically what we want

As part of the big bug review for 16.04 LTS I have tested this on 15.10 and the bug is still there.