pentix
commented
3 years ago Hi Ferdinand
This is intentional, although I agree it might seem a bit misleading and the raison d'être of the "show bootlog" button could be clearer.
The idea is that most people open qjournalctl and just click on the "Show the current bootlog" button, to see the current log (i.e. the one of this exact system boot). This requires exactly one click and enables realtime following by default.
Another use case might be that a user wants to see system logs from previous boots. In that case, the "List all available boots" button is used, which presents all available (archived) logs. You can then select a boot from the list, reverse the output if you like and use the "show boot log" button, to get the results. Obviously, the "realtime following" is disabled, if you look at an archived log.
I hope that explains why you're looking at disabled checkboxes, it's definitely not you missing something during compilation, there are no advanced switches/flags during compile time.
[ The only reason I didn't want to list all boots by default (and make this all a lot more obvious) is that if your you've got a lot of archived logs, it takes quite a few seconds to read all the available logs, which is a terrible startup delay and feels like an eternity if you just open qjournalctl because you want to look at the current boot log... ]
I hope this helps!
fethomm
Like the headline says. We compiled QJournalctl from GitHub on Debian Sid and Fedora 34 and on both the checkboxes have no function at all. Besides that, we could not figure out, what 'Show bootlog' was supposed to do exactly, because it also does nothing. Did we miss something during compilation?