Overwrite journald to log in the embedded terminal!

Hi,

I'm only now hitting this issue because i'm usually developing in a project where a log handler class is installed.

Now i made a very simple clean QML project with this:

import QtQuick 2.12
import QtQuick.Window 2.12

Window {
    width: 640
    height: 480
    visible: true
    title: qsTr("Hello World")

    Component.onCompleted: {
        console.log("Why is this not showing up?")
    }
}

On a system where Qt is compiled with -journald and where "Run in terminal" is disabled for the project run settings the logging lines will not show up at all.

If it's run in a terminal they will.

If "journalctl -f" is run, it will show up there too.

If besides run (CTRL + R) "Start debugging" is chosen then the log does show up in the "QML Debugger Console" tab too.

While those are quite some options to get the logging to show, neither is developer friendly in my opinion. The last option i mentioned above is only useful if you want to set breakpoints in QML. It's not very useful (because it slows everything) for just adding some "console.log" lines.

I'm expecting the application log output to happen in the same window where i'm debugging stuff. So that will be in the "Application Output" tab of QtCreator.

Note that i'm definitely not the first one with this issue. You can google for things like "qml console.log not working" and you'll find some hits. Here in the bug tracker you can find some too. Like #QTCREATORBUG-20051.

Now i suspect this issue is a bit of a mixture of events and i suspect i'm going to be pointed to "fix it at your distribution".. That's fine, but then please do tell me what i should tell them. As to me this should be dead simple, i put a console.log line in code that i run in QtCreator so QtCreator should show it (and definitely in debug mode!). Period. Something (journald) somewhere prevents that logic from being true but i have no idea how to tweak it that it works how i just described it should.

Cheers,
Mark