Reindl Harald wrote:
>
>
>
> Am 05.08.2016 um 10:58 schrieb Reindl Harald:
>> Am 05.08.2016 um 00:45 schrieb Reindl Harald:
>>>
>>>
>>> Am 05.08.2016 um 00:39 schrieb Rex Dieter:
>>>> Reindl Harald wrote:
>>>>
>>>>
>>>>>> I cannot explain the difference in behavior, I would expect F23 to
>>>>>> be the
>>>>>> same as F24 in this regard
>>>>>
>>>>> i expected too - but it's fact and as you can see on this list when
>>>>> you look closer i am not the only one where KDE currently floods logs
>>>>
>>>> So, *if* there's a bug here, the bug is that F23 isn't logging
>>>> warnings...
>>>> as expected
>>>
>>> come on than the bug is that for a single login witha few autostarting
>>> applications hundret lines of logging are produced instead get all this
>>> warnings fixe din the code
>
> that ones are also "terrible helpful" - should i now patch the
> so-binaries with a hexeditor or why do i care about that stuff *in a
> release version* and so it goes on and on
>
> inspired by systemd logspamming seems to become the new global IT
> problem and *es it is harmful* because i don't see important stuff which
> *really* needs my attention in that wood of crap
>
> Aug 4 16:58:58 rh kdeinit5: kf5.kded: No X-KDE-DBus-ServiceName found
> in "/usr/lib64/qt5/plugins/kf5/kded/proxyscout.so"
kf5-kded/kded-5.24.0/src/kded.cpp: qCWarning(KDED) << "No X-KDE-
DBus-ServiceName found in" << metaData.fileName();
filterable by using:
*.warning=false
>> Aug 4 17:44:14 rh ksmserver: Could not resolve property :
>> radialGradient3118
Another case of unfilterable qWarning, this one comes from qt5-qtsvg:
src/svg/qsvgstyle.cpp: qWarning("Could not resolve property :
%s", qPrintable(m_link));
src/svg/qsvghandler.cpp: qWarning("Could not resolve property
: %s", qPrintable(id));
src/svg/qsvghandler.cpp: qWarning("Could not resolve property
: %s", qPrintable(id));
-- Rex
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/kde@xxxxxxxxxxxxxxxxxxxxxxx
