https://bugs.kde.org/show_bug.cgi?id=449918
--- Comment #2 from David Edmundson <k...@davidedmundson.co.uk> ---
>Good catch, looks like that's exactly what happens.
>`fontsCfg.readEntry(fontDpiKey, 0)` means "fall back to 0 if fontDpiKey isn't
>found". And then that 0 gets unconditionally written out.
Just above we have:
if (!fontsCfg.hasKey(fontDpiKey)) {
return;
}
It means there is a key with this set to 0 set by someone.
So similar bug, but not the fault of my patch (obviously :D )
--
You are receiving this mail because:
You are watching all bug changes.
