mirror of
https://github.com/logos-co/logos-standalone-app.git
synced 2026-08-27 10:01:07 +00:00
Dario Gabriel LipicarandClaude Opus 5
5fc709ed69
Qt's default message handler prefers journald/syslog where the platform offers it, so this app's own qInfo()/qWarning() went somewhere nobody was looking. The cost is not cosmetic. Launching with a broken plugin printed NOTHING -- not 'No metadata.json or manifest.json in plugin directory', not 'Failed to load QML', not 'Timeout waiting for ui-host ready' -- while the window showed only a bare 'Failed to load UI plugin'. Every diagnostic this app already writes was invisible, including the one naming the exact QML line at fault. That is worse than having no diagnostics: an absent warning reads like a passed check, so it actively misleads. It cost me a long detour into a non-existent ui-host startup bug before I found the real one-line QML error that the app had been reporting all along. Set before QApplication so it lands before the logging backend is first used, and only when the caller has not chosen for themselves -- exporting QT_FORCE_STDERR_LOGGING=0 still suppresses. VERIFIED: with no env var, 'No metadata.json ... in plugin directory' now appears on stderr; with QT_FORCE_STDERR_LOGGING=0 it is still suppressed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>