Comment # 17 on bug 1210029 from Carlos Robinson

For the record, journalctl almost provoked me to submit a wrong journal log.

Beta:~ # journalctl --list-boots
 -8 bff43e3dd735461f9c2f451dca7a8486 Sat 2023-04-01 22:47:51 CEST���������Sat
2023-04-01 22:51:11 CEST
 -7 dec62252db9c46ebb99c7fd03d32a4ae Sat 2023-04-01 22:51:40 CEST���������Sat
2023-04-01 23:05:37 CEST
 -6 6409ed7781ea4b81bf07f3f5a4d936a4 Sun 2023-04-02 20:33:34 CEST���������Sun
2023-04-02 20:55:18 CEST
 -5 babb6dd2ea3c459ea9ece85a11559b0a Sun 2023-04-02 20:55:44 CEST���������Sun
2023-04-02 21:08:05 CEST
 -4 8de7405b36ac41e285b414cf03398c2d Sun 2023-04-02 21:08:31 CEST���������Mon
2023-04-03 03:35:48 CEST
 -3 152f444cc6fc44b88966d65084e6ba73 Tue 2023-04-04 11:51:35 CEST���������Tue
2023-04-04 12:04:15 CEST
 -2 b57a7bc3a06a4ba8b4e485aa810c3b35 Tue 2023-04-04 12:04:47 CEST���������Tue
2023-04-04 12:08:21 CEST
 -1 2a3034c8668a4897b0e857e611bde4ee Tue 2023-04-04 12:09:03 CEST���������Tue
2023-04-04 12:13:36 CEST
  0 8d19714585b04128a46562b917a621fb Tue 2023-04-04 12:14:13 CEST���������Tue
2023-04-04 12:17:53 CEST
Beta:~ # 

The command "journalctl -b0" produces the right log:

Apr 04 12:14:13 Beta kernel: Linux version 5.14.21-150500.3.gad9a743-default
(geeko@buildhost)...

But "journalctl -b1" produces apparently log #8 instead:

Apr 01 22:47:51 Beta kernel: Linux version 5.14.21-150500.1.ga8add28-default
(geeko@buildhost) ...

I had to use "journalctl -b 8d19714585b04128a46562b917a621fb" instead. If one
of the provided logs is wrong, that is the reason.