7388 2015-03-03 20:54:58 +0000 The systemd journal is empty. 2015-03-26 10:16:15 +0000 1 1 11 Runtime General Runtime General Runtime unspecified x86 x86_64 VERIFIED FIXED Medium+ major 1.8 M4 1 randy.e.witt randy.e.witt alexandru.c.georgescu richard.purdie sgw alexandru.c.georgescu --- Regression (Used to work) No (bug/feature does not impact docs) oldest_to_newest 49165 0 randy.e.witt 2015-03-03 20:54:58 +0000 Running journalctl after boot produces no results and is empty. This is on core-image-sato built using 5c1c8af083ca7b57cc339d16ce0513b27c5dac90 from poky master. This was tested using "runqemu qemux86-64 core-image-sato ext4" 49182 1 randy.e.witt 2015-03-04 18:11:32 +0000 I'm marking this a duplicate of 7393 because I believe the journal is empty as a side effect of the failures in 7393. If the journal is restarted after boot, it is appears to start working. *** This bug has been marked as a duplicate of bug 7393 *** 49243 2 randy.e.witt 2015-03-06 02:04:13 +0000 This is actually a different issue than what is in bug 7393. 49759 3 randy.e.witt 2015-03-25 17:08:10 +0000 This should be fixed in master: commit d2690754febcaff134de2085294af4561c1d9214 Author: Randy Witt <randy.e.witt@linux.intel.com> Date: Tue Mar 24 10:26:36 2015 -0700 You can test it manually by making sure that the command "journalctl" contains information. I also added a test called test_systemd_journal to the testimage tests. 49791 4 alexandru.c.georgescu 2015-03-26 10:16:15 +0000 I can now see journalctl log. Tested with core-image-minimal + systemd on fido:8b3d3e7c957ad06c390886487f69aeb8e145da6a