[Pkg-utopia-maintainers] Bug#672358: dbus: some machines do not shutdown properly and do not do poweroff

[Simon McVittie]

On 10/05/12 11:56, Jürgen Kaiser wrote:
> With debian wheezy (testing), last dist-upgrade 09.05.2012, on all
> type of machines, I have got problems with full shutdown by running
>
> shutdown -h now
> or
> shutdown -hP now
[...]
> At least I inspect the run level and found that there is no dbus kill
> link in run level 0 for dbus.
>
> I added a link to stop dbus lately after kdm and after adding this
> kill link the shutdown process finished successfully.
>
> Please enter proper stop directives (0 1 6) to lsb header in init
> script and postinst script to honor this change.

As far as I understand it, what dbus does (no explicit stop directives)
is meant to work, and is correct for anything that doesn't need to do
special cleanup during shutdown - having init kill all the remaining
processes with a single syscall is more efficient than running shell
scripts that kill them individually, leading to a faster shutdown. The
change was made back in 1.1.4-1 for runlevels 0 and 6, and 1.2.24-1 for
runlevel 1, so dbus was already not killed in those runlevels in squeeze.

(anacron, cron, sshd are among other examples of common daemons that
don't have an explicit stop runlevel.)

This might mean that something has changed in dbus and/or init more
recently, such that the way init kills it no longer works? (The same
dbus version worked fine last time I rebooted my laptop, though.)

Alternatively: what upgrade path did you use on the machine where init
stalls waiting for dbus? Did you install wheezy, or install squeeze and
upgrade, or what? Depending on the upgrade path you followed, you might
have ended up with slightly different configuration.

Similarly, did you say you had a similar machine where init *does* kill
dbus properly without any intervention from you? If you do, what version
of Debian did you originally install on that machine, and what upgrade
path did you use there?

> Kernel used is taken from kernel.org without any patches, configuration is 
> taken from debian experimental.

I'd be interested to hear what happens with the packaged Debian kernel
(linux-image-3.2.0-2-amd64 from unstable and/or
linux-image-3.3.0-trunk-amd64 from experimental), if those can boot on
your hardware.

    S