Bug 1331005 - Reasonable QT_LOGGING_RULES as default
Summary: Reasonable QT_LOGGING_RULES as default
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: qt5-qtbase
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-27 12:42 UTC by Jozef Mlich
Modified: 2016-05-02 14:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-27 14:03:40 UTC
Type: Bug


Attachments (Terms of Use)
hello_world.qml (383 bytes, text/plain)
2016-04-27 12:42 UTC, Jozef Mlich
no flags Details

Description Jozef Mlich 2016-04-27 12:42:19 UTC
Created attachment 1151362 [details]
hello_world.qml

Description of problem:
The beginners (and also me) usually starts with console.log("hello world"). In new version of Qt, there was newly introduced QLoggingCategory [1] which allow configuration of verbosity during debugging.

[1] http://doc.qt.io/qt-5/qloggingcategory.html

Reproducer: 
qmlscene hello_world.qml

Expected Result at stdout:
hello log
hello debug

Current result output at stdout is empty.

I suggest to add following configuration into .bash_rc (or /etc/profile) during of installation of qt5-base-devel (or qt5-devel or any other suitable) package:

export "QT_LOGGING_RULES=*=true
qt.*=false"

Comment 1 Rex Dieter 2016-04-27 14:03:40 UTC
see bug #1227295 for some history.

The kde-sig policy decision on distribution default is to show no debug logging via qtlogging.ini : 

[Rules]
*.debug=false

which we know is different from upstream's default of (essentially, I think):
qt.debug=false

You're welcome to start a conversation on 
https://lists.fedoraproject.org/admin/lists/kde.lists.fedoraproject.org/
if you feel like we should consider otherwise.

Comment 2 Jozef Mlich 2016-04-27 14:59:55 UTC
Thank you for explanation and recommendation. I am sorry that I didn't found the ticket previously.


Note You need to log in before you can comment on or make changes to this bug.