I also experienced this bug, because I had the shutdown script order messed up by VMware Workstation. Everything was fixed by manually creating the links to /run and /run/lock as per #18, and restoring the correct shutdown script order as per #22. So, as a side effect of the /run problem, this fixed a long standing problem with the shutdown sequence. I used to stupidly wonder why fsck often reported "orphan nodes deleted" on reboot, now it won't happen any more !
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858122 Title: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
