Bug 86193

Created attachment 109332 [details]
Verbose output of case 1 (concrete boot specified)

'journalctl <some executable>' misses entries depending on other arguments.
In contrast if no executable is specified, listed entries (filtered with 'grep') are complete.

'journalctl --verify' does not report any failure.

I noticed this bug with version 216-3 and just confirmed it with version version 217 bundled with Arch Linux.


Case 1: Entry of thunderbird is only listed if concrete boot is specified:
(please refer to attachment for verbose output)
----------------------------
root@laurin:~# journalctl -b bd67248b3a964252a0e14fe6adb0620f /lib/systemd/systemd-coredump
-- Logs begin at Tue 2014-09-09 16:09:26 CEST, end at Wed 2014-11-12 11:13:36 CET. --
Oct 30 06:24:48 laurin systemd-coredump[4788]: Process 464 (thunderbird) of user 1000 dumped core.
Oct 30 07:38:30 laurin systemd-coredump[5389]: Process 5388 (cat) of user 0 dumped core.
Oct 30 08:31:13 laurin systemd-coredump[5700]: Process 5699 (cat) of user 0 dumped core.
----------------------------
root@laurin:~# journalctl /lib/systemd/systemd-coredump                   
-- Logs begin at Tue 2014-09-09 16:09:26 CEST, end at Wed 2014-11-12 11:13:36 CET. --
[...]
-- Reboot --
Oct 20 08:40:32 laurin systemd-coredump[6898]: Process 2484 (luminance-hdr) of user 1000 dumped core.
Oct 20 10:18:30 laurin systemd-coredump[10249]: Process 1693 (hugin) of user 1000 dumped core.
Oct 20 10:32:49 laurin systemd-coredump[10739]: Process 10738 (feh) of user 1000 dumped core.
Oct 20 11:24:57 laurin systemd-coredump[11002]: Process 10999 (feh) of user 1000 dumped core.
-- Reboot --
Oct 28 08:56:45 laurin systemd-coredump[1959]: Process 1958 (light-locker) of user 0 dumped core.
-- Reboot --
Oct 30 07:38:30 laurin systemd-coredump[5389]: Process 5388 (cat) of user 0 dumped core.
Oct 30 08:31:13 laurin systemd-coredump[5700]: Process 5699 (cat) of user 0 dumped core.
----------------------------


Case 2: Inconsistent output using '--since'; Listing of Oct 28th is not a superset of Oct 30th.
(No difference if '_EXE=/usr/lib/systemd/systemd-coredump' is used.)
----------------------------
root@laurin:~# journalctl --since=2014-10-28 /lib/systemd/systemd-coredump
-- Logs begin at Tue 2014-09-09 16:09:26 CEST, end at Wed 2014-11-12 11:13:36 CET. --
Oct 28 08:56:45 laurin systemd-coredump[1959]: Process 1958 (light-locker) of user 0 dumped core.
-- Reboot --
Oct 30 07:38:30 laurin systemd-coredump[5389]: Process 5388 (cat) of user 0 dumped core.
Oct 30 08:31:13 laurin systemd-coredump[5700]: Process 5699 (cat) of user 0 dumped core.
----------------------------
root@laurin:~# journalctl --since=2014-10-30 /lib/systemd/systemd-coredump
-- Logs begin at Tue 2014-09-09 16:09:26 CEST, end at Wed 2014-11-12 11:13:36 CET. --
Oct 30 06:24:48 laurin systemd-coredump[4788]: Process 464 (thunderbird) of user 1000 dumped core.
Oct 30 07:38:30 laurin systemd-coredump[5389]: Process 5388 (cat) of user 0 dumped core.
Oct 30 08:31:13 laurin systemd-coredump[5700]: Process 5699 (cat) of user 0 dumped core.
-- Reboot --
Nov 04 16:37:45 laurin systemd-coredump[4163]: Process 3657 (evince) of user 1000 dumped core.
-- Reboot --
Nov 11 15:28:36 laurin systemd-coredump[8148]: Process 7965 (thunderbird) of user 1000 dumped core.
----------------------------

Maybe this bug report is related: https://bugs.freedesktop.org/show_bug.cgi?id=64296


Regards,
doak