Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65089 - [kalarm] Upgrade to qt5.14.0 broke non-anti-aliased fonts
Attached to Project:
Arch Linux
Opened by David Rosenstrauch (darose) - Wednesday, 08 January 2020, 23:12 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 09 January 2020, 09:10 GMT
Opened by David Rosenstrauch (darose) - Wednesday, 08 January 2020, 23:12 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 09 January 2020, 09:10 GMT
|
DetailsThe upgrade to qt5.14.0 in mid-to-late December broke some functionality in Kalarm. It used to be that when kalarm launched, it would pick up all the same font and style settings I had set for all my KDE and QT apps. Now it picks up the style settings, and perhaps 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 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.
Additional info: * kalarm 19.12.0-1 |
This task depends upon
Comment by Antonio Rojas (arojas) -
Thursday, 09 January 2020, 09:10 GMT
We are not modifying the package in any way, so please report this upstream. Check with a clean user first to make sure it's not a configuration issue.