Bug 1377116

Summary: qtlogging.ini is not working rant
Product: [Fedora] Fedora Reporter: NN <vgv>
Component: qt5-qtbaseAssignee: Than Ngo <than>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: davejohansen, helio, itamar, jgrulich, jreznik, manisandro, rdieter, rnovacek, than, vgv
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-02 15:49:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description NN 2016-09-18 16:42:44 UTC 
Description of problem:

changing qtlogging.ini doesn't work and hasn't worked since implemented 3 months ago.
i did change the Rules to true under both:
/etc/xdg/../qtlogging.ini
~/.config/.../qtlogging.ini
rm -r both of those files doesn't make a change either.

that's fine! I can replace qdebug with std::cout in qt, but...
making qml apps in fedora is pretty much impossible now. there is no way to test advanced variant signals from c++ to qml without console.log output. also, qml applications are very fragile about binding loops, now those warnings are gone. 

another thing, doesn't kde use their own debugger? so what is this "spam in logfiles" crusade all about? if anyone it's kde people who abuse it, not people who learn programming from youtube/qt wiki tutorials. worst of all there is not a single line about this change in fedora release docs.

how is this even a "workstation" release if it's impossible to work with? please stop this nonsense.
Comment 1 Rex Dieter 2016-09-18 23:18:33 UTC 
don't use ..., please include full paths, and the contents of qtlogging.ini of what you tried... mostly so I can try to reproduce your results (since last time I tested this, it worked advertised for me).
Comment 2 Rex Dieter 2016-09-26 15:02:49 UTC 
ping, please provide information requested in comment #1

will wait one more week before closing->insufficient_data
Comment 3 Than Ngo 2016-11-02 15:49:41 UTC 
I'm closing that bugzilla INSUFFICIENT_DATA because there's no testcase to reproduce this issue.  Feel free to reopen it once you find some way how to reproduce it.