You are not logged in.
Hullo,
For no apparent reason (I don't recall installing anything which could've caused this), certain characters on Firefox and Atom have become rather messed up. An example for some code on GitHub is shown below (Firefox, but a similar effect is also observable in Atom):
http://i.imgur.com/iRedjWU.png
Any ideas as to what could've caused this, or what I could do to fix it?
Last edited by jasonwryan (2016-07-31 18:08:55)
Offline
Read the Code of Conduct and only post thumbnails http://wiki.archlinux.org/index.php/Cod … s_and_code
What have you updated? What fonts do you have installed? Locale? etc...
Moving to NC.
Offline
Understood.
According to /var/log/pacman.log, gsfonts was recently updated. Could that be what's causing the issue?
No additional fonts were manually installed (FF/Atom might've when I installed them a while ago). Locale is en_GB.UTF-8.
Offline
https://git.archlinux.org/svntogit/pack … a553e3cc54
You'll need to install fonts to match those that Github uses, or force local ones in Firefox (no idea how Atom works).
Offline
It's more than just GitHub:
Offline
Fixed this issue by downgrading the package to the original one, which worked fine. What should I do about the weird issue with the updated package, if anything?
Offline
I'm having exactly this same problem. Using dwm with Icon and monospace fonts and everything is garbled in exactly the same way as the OP's image shows. Firefox text input boxes also showing the same.
Downgrading gsfonts fixes the issue and everything displays normally again.
Any ideas to try for a real fix?
Offline
The real fix is to install fonts that match those specified by those websites, or set up your fonts config to replace them with ones you have installed.
Offline
20160531-1 upstream update, ships t1/ttf/otf not pfb/pfm
20160531-2 type1 should be superseded by otf
20160531-3 fix install scriptlet
Determining which of the above releases was the first to exhibit broken font rendering behavior may help point to the cause.
Possible causes include:
Font config's font matching is handling the otf fonts differently than the type1 fonts that are no longer shipped so the otf fonts are never used.
The otf fonts are matched but the correct glyph cannot be found so a substitute font is used instead.
Offline
I finally had a chance to figure this out. It looks like the mapping for 'monospace' is buggered up somehow.
Old gsfonts:
# fc-match "monospace"
n022003l.pfb: "Nimbus Mono" "Regular"
New gsfonts:
# fc-match "monospace"
D050000L.otf: "D050000L" "Regular"
I'm not sure exactly what 'D05000L' refers to, so I simply changed my /etc/fonts/conf.avail/51-loca.conf and added:
<alias>
<family>monospace</family>
<prefer><family>Noto Mono</family></prefer>
<default><family>fixed</family></default>
</alias>
Then run fc-cache and viola, good to go.
The alternative is to add a monospace font that is installed to .Xresources, Firefox prefs, etc and that also worked.
HTH.
Last edited by jcarneal (2016-08-14 17:02:41)
Offline