Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53579 - [qtcreator] 4.2.1-4 regresses back to FS#40583

Attached to Project: Arch Linux
Opened by Lester Godwin (legiv) - Wednesday, 05 April 2017, 21:46 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 24 May 2017, 18:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Antonio Rojas (arojas)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

qDebug() messages are not displayed.

Additional info:
Downgrading to 4.2.1-3 or adding environment variable QT_LOGGING_TO_CONSOLE=1 with 4.2.1-4 prior to executing qtcreator executable corrects the problem.


Steps to reproduce:

Start qtcreator qDebug() messages do not print to qtcreator console. They do print when program executed outside of qtcreator.
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 24 May 2017, 18:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  qtcreator 4.3.0
Comment by Antonio Rojas (arojas) - Thursday, 06 April 2017, 15:17 GMT
qtcreator has journald support since 3.4, and the example from  FS#40583  works for me. Can you attach a non-working code example?
Comment by Lester Godwin (legiv) - Thursday, 06 April 2017, 16:21 GMT
Attached is a little test project I'm working on for a double edit box. Select project and uses all default settings. My Arch system is fully up-to-date. Included qDebug() statements do not display unless I add the QT_LOGGING_TO_CONSOLE=1 environment variable when starting qtcreator.

Thanks!
(application/x-gzip)    doubleedit.tgz (2 KiB)
Comment by Antonio Rojas (arojas) - Thursday, 06 April 2017, 16:28 GMT
As you can see, debug output is displayed correctly here.
   qtcreator.png (40.3 KiB)
Comment by Lester Godwin (legiv) - Thursday, 06 April 2017, 16:31 GMT
Well obviously something is special about either your or my setup. I will try deleting my qtcreator settings and see what happens with a fresh start.
Comment by Lester Godwin (legiv) - Thursday, 06 April 2017, 21:16 GMT
I deleted my ~/.config/QtProject directory and tried again. The messages still do not print without the QT_LOGGING_TO_CONSOLE=1 set. So the problem is apparently somewhere else. I will try to look into what this variable is actually doing to see if I can isolate the problem.
Comment by Antonio Rojas (arojas) - Thursday, 06 April 2017, 21:29 GMT
Do you use the standard Qt packages? Do the debug messages show in the journal?
Comment by Lester Godwin (legiv) - Friday, 07 April 2017, 01:28 GMT
I use the standard package, and yes, the debug messages show in the journal.
Comment by Urs Fleisch (ufleisch) - Saturday, 20 May 2017, 11:28 GMT
I have the same issue here. When starting a program with the debugger in Qt Creator, all qDebug(), qWarning() output is only available in the systemd journal. When starting without debugger, the output is visible in the "Application Output" pane and still with journalctl, so the Qt Creator JournaldWatcher seems to work in that case. The workaround is to set QT_LOGGING_TO_CONSOLE=1 in the "Run Environment" of the Qt Creator project settings.

When looking at https://bugreports.qt.io/browse/QTCREATORBUG-16495, the bug seems old and unresolved, but I have the feeling that this was working before.
Comment by Antonio Rojas (arojas) - Saturday, 20 May 2017, 11:55 GMT
So this is only reproducible when debugging? Then it is unrelated to  FS#40583 
Comment by Antonio Rojas (arojas) - Wednesday, 24 May 2017, 18:49 GMT
This works fine in 4.3, both in running and debugging mode.

Loading...