Bug 1396746

Summary: Empty components list
Product: [Fedora] Fedora Reporter: Germano Massullo <germano.massullo>
Component: kdebugsettingsAssignee: Daniel Vrátil <me>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: kde-sig, luigi.toscano, me, rdieter
Target Milestone: ---Keywords: Reopened
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: 2017-02-02 18:09:43 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:
Attachments:
Description Flags
screenshot none

Description Germano Massullo 2016-11-19 15:33:37 UTC
Created attachment 1222162 [details]
screenshot

Description of problem:
kdebugsettings has an empty components list. See screenshot.
I solved by adding 

kf5.kio.core.debug=true
kf5.kio.widgets.debug=true
kf5.kiod.debug=true

into
~/.config/QtProject/qtlogging.ini

Version-Release number of selected component (if applicable):
kdebugsettings.x86_64 16.08.2-1.fc24

Comment 1 Rex Dieter 2016-11-19 15:55:46 UTC
I cannot reproduce this, apparently.  my kdebugsettings is non-empty without any custom ~/.config/QtProject/qtlogging.ini

Comment 2 Rex Dieter 2016-12-02 14:02:41 UTC
I don't recall, is this reported upstream yet?  If not, please consider doing so.

Comment 3 Luigi Toscano 2017-02-02 00:06:36 UTC
Someone else this, and it was fixed in the Applications/16.12 branch:

https://commits.kde.org/kdebugsettings/50890b9654278647e9e34e403a3c1ac921c24c12

Comment 4 Rex Dieter 2017-02-02 14:04:41 UTC
thanks!

I'll mark this closed->nextrelease (abusing it, kde-apps-16.12.1 update will come soonish)

Comment 5 Rex Dieter 2017-02-02 14:18:15 UTC
And... re-reading the commit, makes me wonder if there's still a bug somewhere, since we actually *do* have a qtlogging.ini file, it's just in a different location (which this code may not handle... reading code now).

Comment 6 Rex Dieter 2017-02-02 18:09:43 UTC
upstreamed,
https://phabricator.kde.org/D4407

(and candidate patch applied to our packaging)

ok, closing again :)