Just a thought - and I am the first to admit my limited knowledge - but maybe it is not completely the code that is shutting down the system that is causing the issue. Maybe the more recent version of upstart is somehow creating a system state that is not created by the earlier version of upstart. and it is this system state that is not handled correctly by the code that shuts down the system. I.e. the code that shuts down the system could be identical, but maybe it is trying to handle a state that does not exist when the earlier version of upstart is used. I have no idea whether that is possible . . . just thinking out loud. I.e. it is an interaction, not just the upstart code.
-- failure to umount local filesystems - gutsy tribe 2 https://bugs.launchpad.net/bugs/125702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
