Here are the requested logs: Normal boot: journal http://paste.ubuntu.com/11801096/ jobs.txt http://paste.ubuntu.com/11801103/ failed.txt http://paste.ubuntu.com/11801107/
During a normal boot, I observe no issues. The directory is created as it should, and network-manager starts successfully. You noticed that the logs I sent previously (from recovery mode) claim that systemd-tpmfiles is not started, because it waits for local-fs, which makes perfect sense, as [usually] filesystems are not mounted in recovery mode. However, my original problem was that I was not able to start network-manager in recovery mode. When enabling networking from the recovery menu, file systems get mounted, so systemd-tmpfiles should start afterwards. The logs I have attached to my previous comment are from a boot into recovery mode *without* networking, which is why fs are not mounted. I have repeated the procedure when booting into recovery mode *with* networking enabled from the recovery menu (in such case the /run/sendsigs.omit.d directory is still missing, even though filesystems should be mounted) - below I attach logs from such boot. Recovery mode with networking enabled: systemctl status -l systemd-tmpfiles-setup.service http://paste.ubuntu.com/11801094/ journalctl -b http://paste.ubuntu.com/11801088/ I hope this makes a bit more sense now. ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- 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
