Comment 9 for bug 294389

The current theory for this bug is that the system-tools-backends daemon gets restarted (by DBUS) sometime after dpkg stops the daemon in order to perform the upgrade. This will then cause the init script to fail when the package is configured and it tries to start the daemon again (which shouldn't happen anyway).

If that is the case then this is not a problem in Jaunty, as the latest version includes a check in the init script to see if system-tools-backends is already running before it tries to start it again with start-stop-daemon.

However, for this failure to happen, something has to send a message to the system tools backends service over the system bus. This could happen by opening any one of these tools: time-admin, users-admin, shares-admin, network-admin or services-admin. Does anyone who experienced this problem remember what else they were doing at the time that the package was upgraded? If so, then that might be a great help.

Thanks