https://bugs.kde.org/show_bug.cgi?id=513120
--- Comment #2 from Andreas Cord-Landwehr <[email protected]> --- Thanks a lot for the bug report. This is a very interesting issue, yet hard to see from these information where the problem lies, so I will need to ask some questions first: - with "no longer showing logs past November 30th. Journalctl still works" do you mean that a) you see a boot-id in the drop-down box which contains a period spanning before November 30th" and then in the log entry list the entries are not available? b) or that there is not even a boot-id available for earlier dates? - (trivial, but to exclude this) Please double check that in the "Priority" selection you select Debug to ensure that we no just have simply different default log levels between both apps. - Did you do any software updates between the situation when all logs were available and when the logs became missing before the specified data? If yes, did this software upgrade include kjournald and/or systemd (if possible I need the exact versions) - What is you current version of systemd* (reason is that we parse your journald database by the sd-journal API of the systemd library) - Could you check if this problem also exists with the most recent version of kjournald-browsers which is available via e.g. Flatpak? (tutorial: https://userbase.kde.org/Tutorials/Flatpak or alternative via snap; please note that the name is org.kde.kjournaldbrowser and that is also a legacy discontinued package named differently) -- You are receiving this mail because: You are watching all bug changes.
