[Bug 1431110] Re: network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d

2015-03-12 Thread Michael Marley
The directory is indeed missing. If I run the journalctl command, it just says No journal files were found. (No, I haven't modified the logging configuration.) Running the systemd-tmpfiles command does create that directory. I have attached the output. ** Attachment added:

[Bug 1431110] Re: network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d

2015-03-12 Thread Michael Marley
Interesting, I tried running the journalctl command again and now it works. Here is the output. ** Attachment added: journalctl.log https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431110/+attachment/4342526/+files/journalctl.log -- You received this bug notification because you are

[Bug 1431110] Re: network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d

2015-03-12 Thread Martin Pitt
*** This bug is a duplicate of bug 1431107 *** https://bugs.launchpad.net/bugs/1431107 Same boot cycles as in bug 1431107, so I'll mark these as dupes. ** This bug has been marked a duplicate of bug 1431107 ordering cycles with early boot images on lvm2.service -- You received this bug

[Bug 1431110] Re: network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d

2015-03-12 Thread Martin Pitt
Do you actually have a /run/sendsigs.omit.d/ directory after booting? If yes, then this is a race condition at boot, if not, there's something wrong with /usr/lib/tmpfiles.d/debian.conf which creates that directory. I'd like to see a full journalctl -b output. If the directory is missing after