Hi, just want to state that I am struck by this bug for a while now. Just started today searching for a solution.
On Wed, 1 Apr 2015 11:10:21 +0200 Martin Pitt <mp...@debian.org> wrote: > Yesterday we found quite a fundamental flaw related to how D-Bus is > stopped during shutdown [1]. It might be worth a try to edit > /lib/systemd/system/dbus.service and append these two lines to the > [Service] section: > > ExecStop=/bin/true > KillMode=none > > Then run "systemctl daemon-reload" as root. Does this improve shutdown > for any of you? No change in behavior at all. > Note that this is certainly not a magic bullet for all kinds of > shutdown problems, especially since the reports/data here is vague > enough that these might very well be different reasons. But it would > be interesting to see if it makes a difference for any of you. The > Ubuntu bug https://launchpad.net/bugs/1427672 was linked to this > Debian one and found to be fixed with the above D-Bus change. Hmm, from my reading they say (in the end) "Don't do that !". But however, it didn't solve anything here, so I removed the two lines. I waited for a timeout a complete night, nothing happened. I have to tip the reset (hardware) button or press the poweroff knob for 5s. What works is ALT + PrintScreen + REISUB. But still my filesystems (several VMs running) are broken from time to time (e.g. one of the ReiserFS VMs needs a fsck.reiserfs --rebuild-tree, else it denies booting). I have Samba installed (but can't uninstall it for testing), no squid installed. I am on Debian SID amd64 (up-to-date packages). What exactly can I do to help fixing this bug ?
signature.asc
Description: This is a digitally signed message part.