SUMMARY KDE Journald Browser no longer showing logs past November 30th. Journalctl still works, so the logs exist -- the problem is with the GUI browser not being able to find it, apparently. STEPS TO REPRODUCE 1. Open KDE Journald Browser 2. Click the dropdown to select a journal entry OBSERVED RESULT No results past a certain date (in this case 11/30/2025) EXPECTED RESULT I can access recent logs SOFTWARE/OS VERSIONS Operating System: Fedora Linux 43 KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 Kernel Version: 6.17.9-300.fc43.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 32 GiB of RAM (31.2 GiB usable) Graphics Processor: AMD Radeon RX 7800 XT ADDITIONAL INFORMATION When run from terminal (and when checking journalctl), kjournaldbrowser is causing this error to be reported repeatedly: kjournaldbrowser[450550]: qrc:/qt/qml/org/kde/kjournaldbrowser/Main.qml:76:21: TypeError: Cannot read property 'width' of null
Running as sudo makes no difference.
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)