MSGID: <6948dcf2@news.ausics.net> 2f01452e
REPLY: <10iaic2$38m6d$2@dont-email.me> a589a06b
PID: PyGate 1.5.2
TID: PyGate/Linux 1.5.2
CHRS: ASCII 1
TZUTC: 1000
REPLYADDR not@telling.you.invalid
REPLYTO 3:633/10 UUCP
Lawrence D'Oliveiro  wrote:
> On 22 Dec 2025 10:50:06 +1000, Computer Nerd Kev wrote:
>> Lawrence D'Oliveiro  wrote:
>>> On 20 Dec 2025 17:38:15 +1000, Computer Nerd Kev wrote:
>>>> I find journalctl unclean in all the most important respects ...
>>>
>>> If that's what your system is using to record its per-user log
>>> files, then your choices are either a) learn to use it, or b)
>>> switch to a different distro.
>>
>> Already done b), and in fact on Raspberry Pi I have the
>> (non-Systemd) syslog daemon started manually only for debugging, so
>> normally there are no such logs at all.
> 
> So what happens to the diagnostic messages from GUI apps that you run?

They go to the framebuffer console X is started from (Ctrl-Alt-F1),
unless they were started from a terminal window. But those messages
aren't sent to syslog by the GUI applications, maybe your systems
have something extra which does that when GUI programs are started?

Syslog messages go nowhere if there's no syslog daemon running.

-- 
__          __
#_ < |\| |< _#

--- PyGate Linux v1.5.2
 * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700
SEEN-BY: 226/30 227/114 229/110 112 134 200 206 300 317 400 426 428
SEEN-BY: 229/470 616 664 700 705 266/512 291/111 292/854 320/219 322/757
SEEN-BY: 342/200 396/45 460/58 633/10 280 414 418 420 422 509 2744
SEEN-BY: 712/848 770/1 902/26 2320/105 5020/400 5075/35
PATH: 633/10 280 229/426