This bug report is highly confusing, so let me state this more clearly: the plymouthd process is still running at the point where /etc/init.d/umountroot is run in the shutdown process, and it is holding some rw file descriptor stopping / from being remounted ro, thus causing an unclean shutdown (and a longer boot time because the journal needs to be replayed).
I don't know what plymouthd is supposed to be, but I'm pretty sure it should be dead at that point in the shutdown process. For some reason, it is not responding to TERM signals: this should maybe be considered a bug in plymouthd (notwithstanding the thought that plymouthd is a bug in and of itself). I didn't figure out what the offending rw file descriptor was. I also don't know why only certain users are affected (this is probably related to the details in partitioning). The obvious, but ugly, workaround is to edit /etc/init.d/umountroot to add a line such as "/usr/bin/killall -9 plymouthd" at the top of the do_stop() function (probably a good idea to add a couple of "sync"'s around that, too). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019347 Title: A message: "mount: / is busy" appears every time shutting down or rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1019347/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
