Bug 416060 - Upgrade to qt5.14.0 broke non-anti-aliased fonts in kalarm
Summary: Upgrade to qt5.14.0 broke non-anti-aliased fonts in kalarm
Status: RESOLVED UPSTREAM
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-09 17:25 UTC by David Rosenstrauch
Modified: 2020-01-17 16:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Rosenstrauch 2020-01-09 17:25:53 UTC
Arch Linux upgraded to qt v5.14.0 in mid-to-late December.  This QT upgrade seems to have broken some font functionality in Kalarm.

It used to be that when kalarm launched, it would pick up all the same font and style settings I have set for all my KDE and QT apps. Now it picks up the style settings, and perhaps even the font name & size too.  But the anti-aliased settings are ignored.  So even though I disable anti-aliasing everywhere, kalarm still displays the font as anti-aliased.

This problem seems to be limited to kalarm, and does not seem to happen with other KDE and QT apps. (If you look at the screenshot at http://darose.net/Screenshot_2020-01-08_16-58-43.png you can see that kalarm renders using anti-aliasing, while kinfocenter and qps do not.)  Downgrading all the qt5 packages back down to 5.13.2 eliminates the problem.


Arch Linux (kernel 5.4.2)
Kalarm 2.13.1 (KDE Apps 19.12.1)
qt 5.14.0
Comment 1 David Rosenstrauch 2020-01-14 23:45:15 UTC
FYI, Okular seems to suffer from the same issue.  (Though again, most KDE/QT apps do not.)
Comment 3 David Jarvie 2020-01-17 16:49:48 UTC
Thanks for that information.