Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't log messages go in the stderr by default? #162

Closed
ratijas opened this issue Jun 30, 2021 · 0 comments
Closed

Don't log messages go in the stderr by default? #162

ratijas opened this issue Jun 30, 2021 · 0 comments

Comments

@ratijas
Copy link
Collaborator

ratijas commented Jun 30, 2021

Don't they go in the stderr by default?

I mean, they follow the default Qt handler which is also quite configurable with env variable: https://doc.qt.io/qt-5/debug.html#warning-and-debugging-messages / https://doc.qt.io/qt-5/qloggingcategory.html#configuring-categories

Originally posted by @ogoffart in #86 (comment)

After years of looking for a cause or at least a working solution, I have finally been pointed in the right direction. This whole time Qt apps were trying to log into system journal, and not to stdout/stderr. It can be reverted by simply setting QT_LOGGING_TO_CONSOLE environment variable, as suggested in QTCREATORBUG-24756 (check out linked issues and mail thread as well). Note that QT_LOGGING_TO_CONSOLE does NOT appear in the documentation pages linked above.

I filled as issue QTCREATORBUG-25935 for Qt Creator to set it on by default when running apps from IDE.

If I knew it at the time of #86, I'd rather pass logs from Rust to Qt side. But oh well… Now we have a reason to implement it too.

@ratijas ratijas closed this as completed Jun 30, 2021
@woboq woboq locked and limited conversation to collaborators Jun 30, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant