*** This bug is a duplicate of bug 1061639 ***
https://bugs.launchpad.net/bugs/1061639
This is nice, but all you've done here is run through manually stopping
a bunch of stuff, not necessarily in order. What we need to know is
absolutely and only whether the shutdown completes properly and cleanly
with the automated procedure, via upstart.
In other words:
- Does upstart correctly run through rc scripts at shutdown, running sendsigs
somewhere along the way to kill all processes that are *not* spawned by upstart
and that are *not* listed in /run/sendsigs.omit.d;
- Does upstart correctly continue through its events, and properly stop dbus,
which will trigger stopping network-manager and modemmanager.
On other instances you're also removing a whole bunch of packages. It's
impossible to know which is the real cause of the issue if too many
variables change at once -- one package should be removed at a time to
figure out what blocks shutdown, or one upstart service should be
manually stopped before shutdown to see whether it affects the shutdown
procedure.
Regardless, please file a separate bug report if it hasn't already been
done, with the very specific details about the shutdown procedure as it
is *now*, after release, after the ifupdown fix, etc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058987
Title:
In Quantal, the root filesystem is not cleanly unmounted at shutdown
or reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
