https://bugs.kde.org/show_bug.cgi?id=445813
--- Comment #3 from Malte S. Stretz <m...@apache.org> --- (In reply to Harald Sitter from comment #2) > qtpaths is a developer tool, it really shouldn't be called by runtime code. > seeing as it appears not functionally required I guess we can just ignore it. If that's the case I guess I'll open a libproxy issue then. If I read the historical issues correctly while debugging this it looks like somebody once reported a performance issue with libproxy (because it calls kreadconfig5 for each request) and the output from qtpaths is used to find the kioslaverc file and invalidate the cache if it changes (or not cache at all if none was found): https://github.com/libproxy/libproxy/blob/49bc258fd56db6ee0518058129f8fdc7f35a57e8/libproxy/modules/config_kde.cpp#L49 https://github.com/libproxy/libproxy/blob/49bc258fd56db6ee0518058129f8fdc7f35a57e8/libproxy/modules/config_kde.cpp#L201 https://github.com/libproxy/libproxy/blob/49bc258fd56db6ee0518058129f8fdc7f35a57e8/libproxy/modules/config_kde.cpp#L210 -- You are receiving this mail because: You are watching all bug changes.
