For the two of you this will affect :-) : https://utcc.utoronto.ca/~cks/space/blog/linux/Fedora36FontconfigMystery
-Adam
I was recently working with the font picker widget in GTK4 and it severely slowed my system down anytime I opened it. Looking it up online there was a problem with how the Noto fonts were being detected by the system. I wonder if this is an adjacent bug to the one in that post.
Sent from my iPhone
On Jul 3, 2022, at 10:24 AM, Adam Thompson athompso@athompso.net wrote:
For the two of you this will affect :-) : https://utcc.utoronto.ca/~cks/space/blog/linux/Fedora36FontconfigMystery
-Adam _______________________________________________ Roundtable mailing list Roundtable@muug.ca https://muug.ca/mailman/listinfo/roundtable
On 2022-07-03 Adam Thompson wrote:
For the two of you this will affect :-) : https://utcc.utoronto.ca/~cks/space/blog/linux/Fedora36FontconfigMystery
That's crazy. Glad this guy took one for the team to figure this out. Too bad his writing is atrocious :-) But maybe he's EASL.
It's funny, during Fedora 34 (before upgrading to 35) my gnome-term fonts suddenly got "kerned wider" and I had to screw around with fonts and resize all my default/programmed window sizes to fit on the screen properly.
I bet it wasn't necessarily the 35->36 change that did this, but a change in versions of the underlying rpms, which also got pushed to F34 (and 35, and 36). He just made the switch at the "wrong" time.
However, this does allow me to try his fix to see the effect... On the flipside, this new whatever-fedora-did setup allowed me to switch my terminal font from mono 9 to mono 8 and still be legible on my semi-high-density monitors. Something about how the math works on 9 that makes many mono letters look ugly and harder to read: at least with the new fonts/setup.
-
Adam Thompson -
Chris Schick -
Trevor Cordes