Bug 482928 - Font rendering is weird on scaled displays
Summary: Font rendering is weird on scaled displays
Status: RESOLVED DUPLICATE of bug 479891
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 6.0.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-08 22:30 UTC by Naomi Calabretta
Modified: 2024-03-10 20:56 UTC (History)
2 users (show)

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

Attachments
Screenshot of font rendering (22.03 KB, image/jpeg)
2024-03-08 22:30 UTC, Naomi Calabretta 		Details
Bold and normal weight font comparison (14.12 KB, image/png)
2024-03-10 10:08 UTC, Rune 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Naomi Calabretta 2024-03-08 22:30:14 UTC 
Created attachment 166742 [details]
Screenshot of font rendering

SUMMARY
System settings (and also the shell) render fonts wonkily, specifically on a scaled screen (mine is a 4k screen set at 150%).

STEPS TO REPRODUCE
1. Open System Settings with a font where this is easily noticeable. I used Urbanist, SF Pro Display and Segoe UI.
2. Observe the font rendering

OBSERVED RESULT
Misaligned characters

EXPECTED RESULT
Smooth rendering

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Artix Linux
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Not applicable
Comment 1 Rune 2024-03-10 10:08:04 UTC 
Created attachment 166856 [details]
Bold and normal weight font comparison
Comment 2 Rune 2024-03-10 10:08:43 UTC 
I can reproduce this. It seems to be worse for higher font weights (see attachment).
Comment 3 Rune 2024-03-10 10:11:33 UTC 
This problem does not occur for all fonts. For the (default?) DejaVu Sans, font rendering is fine. Using Inter or IBM Plex Sans, the font rendering is weird as described.
Comment 4 Nate Graham 2024-03-10 20:56:04 UTC 

*** This bug has been marked as a duplicate of bug 479891 ***