[arch-general] QT5 upgrades broke (non-antialiased) fonts
Recently, a couple of KDE apps I use - most notably kalarm - have gotten their fonts screwed up. I usually use non-antialiased fonts. But it looks like now kalarm (as well as the kde control center) is now using anti-aliased fonts. I have them set to disabled in the kde control center, but that seems to be getting ignored. I noticed some recent qt5 packages got upgraded, and am assuming that might be the culprit, though it looks like there were also some kde packages upgraded recently as well. Anyone know what might have broken / how to fix? Thanks, DR
On 12/23/19 11:28 AM, David Rosenstrauch wrote:
Recently, a couple of KDE apps I use - most notably kalarm - have gotten their fonts screwed up. I usually use non-antialiased fonts. But it looks like now kalarm (as well as the kde control center) is now using anti-aliased fonts. I have them set to disabled in the kde control center, but that seems to be getting ignored. I noticed some recent qt5 packages got upgraded, and am assuming that might be the culprit, though it looks like there were also some kde packages upgraded recently as well. Anyone know what might have broken / how to fix?
Thanks,
DR
Apparently it something in the following package upgrades that caused the breakage: akonadi-19.12.0-2 libakonadi-19.12.0-2 python-pyqt5-5.14.0-3 qt5-base-5.14.0-1 qt5-declarative-5.14.0-2 qt5-graphicaleffects-5.14.0-1 qt5-location-5.14.0-1 qt5-multimedia-5.14.0-1 qt5-networkauth-5.14.0-1 qt5-quickcontrols-5.14.0-1 qt5-quickcontrols2-5.14.0-1 qt5-script-5.14.0-1 qt5-sensors-5.14.0-1 qt5-speech-5.14.0-1 qt5-svg-5.14.0-1 qt5-tools-5.14.0-1 qt5-webchannel-5.14.0-1 qt5-webengine-5.14.0-1 qt5-webkit-5.212.0alpha3-8 qt5-x11extras-5.14.0-1 qt5-xmlpatterns-5.14.0-1 qt5ct-0.41-2 When I downgrade that set, the problem goes away. DR
Hi DR,
Recently, a couple of KDE apps I use - most notably kalarm - have gotten their fonts screwed up. I usually use non-antialiased fonts.
As in bitmap fonts? Could it be anything to do with KDE's adjustment for the Pango change that dropped support for bitmap fonts? https://gitlab.gnome.org/GNOME/pango/issues/386 -- Cheers, Ralph.
On 12/24/19 9:04 AM, Ralph Corderoy wrote:
Hi DR,
Recently, a couple of KDE apps I use - most notably kalarm - have gotten their fonts screwed up. I usually use non-antialiased fonts.
As in bitmap fonts? Could it be anything to do with KDE's adjustment for the Pango change that dropped support for bitmap fonts? https://gitlab.gnome.org/GNOME/pango/issues/386
No this isn't due to bitmap fonts. The font in question is a TTF. (Arial from ttf-ms-fonts.) Issue seems to be that after upgrading to qt 5.14.0, kalarm ignores the settings to not antialias the font. When I downgrade back to 5.13.2, the problem goes away. DR
On 12/24/19 10:54 AM, David Rosenstrauch wrote:
On 12/24/19 9:04 AM, Ralph Corderoy wrote:
Hi DR,
Recently, a couple of KDE apps I use - most notably kalarm - have gotten their fonts screwed up. I usually use non-antialiased fonts.
As in bitmap fonts? Could it be anything to do with KDE's adjustment for the Pango change that dropped support for bitmap fonts? https://gitlab.gnome.org/GNOME/pango/issues/386
No this isn't due to bitmap fonts. The font in question is a TTF. (Arial from ttf-ms-fonts.)
Issue seems to be that after upgrading to qt 5.14.0, kalarm ignores the settings to not antialias the font. When I downgrade back to 5.13.2, the problem goes away.
DR
Following up on a previous thread, as I still haven't been able to solve this issue. In the screenshot at http://darose.net/Screenshot_2020-01-08_16-58-43.png you can see that kalarm is using anti-aliased fonts, while other KDE and QT5 based apps (like kinfocenter and qps) both correctly display the non-anti-aliased ones. When I launch kalarm at the command line, it does say "qt5ct: using qt5ct plugin", as it should. But I'm still pretty stumped about what in the qt 5.14 upgrade caused this to break. Any pointers appreciated! DR
participants (2)
-
David Rosenstrauch
-
Ralph Corderoy