To some bold fonts, hinting is not applicable. The same thing happens in the dolphin. Examples: https://yadi.sk/i/QgZtQ19A3YVUkM https://yadi.sk/i/9Dg7EnGc3YVUsF
Do you have anti-aliasing explicitly disabled for a range of fonts in System Settings > Fonts > Configure? Also, what font are you using? What Qt version? What KDE Frameworks version?
Installed in the VirtualBox default fonts: https://yadi.sk/i/r7sWKzwo3YZcM7 font settings: https://yadi.sk/i/4mmsVmZL3YZcLo System Information: https://yadi.sk/i/l3XG4jJ-3YZcLB
Information from comment #2: Excluded range from anti-aliasing: 0 - 12 Font: Noto Sans 10 System Information: - openSUSE Leap 15.0 running in VirtualBox - Qt 5.9.4 - KDE Frameworks 5.45.0 - Plasma 5.12.5
In the future, please attach images directly rather than using 3rd-party services, which have a tendency to shut down or remove content. > Excluded range from anti-aliasing: 0 - 12 > Font: Noto Sans 10 Wouldn't this mean that the default font is not being anti-aliased at all?
However, for some fonts "hinting" is used, but for other fonts (bold) "hinting" it is not applied. example: https://yadi.sk/i/CE7oAi2U3ZaRVB example 2: https://yadi.sk/i/DUFjz28o3ZaRew example settings: https://yadi.sk/i/6dWgaa9w3ZaRfZ
Can you please attach images directly rather than posting links that will eventually expire and are a pain in the neck to download from? I'm not actually able to download any of them for some reason. See https://community.kde.org/Get_Involved/Bug_Reporting#Screenshots_and_screen_recordings
Created attachment 114146 [details] bed hinting
Created attachment 114147 [details] In one window, hinting is not applied to all fonts.
Created attachment 114148 [details] SMPlayer too.
Thanks. Weird issue. Definitely not in plasmashell though... maybe something with KFontRequester?
Created attachment 115530 [details] The problem can be solved The problem can be solved by deleting the word "Regular" from the file "~/.config/kdeglobals" Section [General]
*** This bug has been marked as a duplicate of bug 378523 ***
*** Bug 401615 has been marked as a duplicate of this bug. ***