Control: severity -1 normal Hello,
2025년 9월 7일 (일) PM 2:15, Chi Zhang <[email protected]>님이 작성: > > Package: fonts-baekmuk > Version: 2.2-13 > Severity: important > > Dear Maintainer, > > After updating Google Chrome (google-chrome-stable 140.0.7339.80-1, and > potentially earlier versions since I had some experimental flags on to > mitigate similar symptoms), font rendering were broken. Please see attached > screenshots. > > I found the fonts-baekmuk package by doing `grep antialias > /etc/fonts/conf.d/*.conf` and noticing it contains lines disabling > anti-aliasing. > > I experimented by purging this package and restarting Google Chrome, and the > problem is solved. I reinstalled the font and restarted Google Chrome again, > and the issue appeared again. > > Please let me know if additional info is needed. Based on the screenshot, I believe the baekmuk font was actually selected and rendered as instructed. I can reproduce this only when I explicitly select baekmuk font in the settings. I have never seen a case with other fonts affected. Maybe that baekmuk fontconfig (decades-old small size workaround in low-res era) can be dropped nowadays. But it won't fix your font selection and still use this ugly font. About the font selection, please file another bug to fontconfig-config.
