So systemd-tmpfiles-setup-dev.service ran fine (don't worry about the
"does not match any include prefix", that's debugging output from setup-
dev), but systemd-tmpfiles-setup.service never actually ran, it seems
its waiting for local-fs.target to get active, which never actually
happens. But if you ran this from rescue mode that's no surprise -- all
this runs way before it. Can you please give me a journal output for a
normal (non-rescue) boot? After such a boot, please log in, do
systemctl list-jobs > jobs.txt
systemctl --failed > failed.txt
and attach jobs.txt and failed.txt here as well. Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467131
Title:
systmd-tmpfiles-setup sometimes not run on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467131/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
