> The third thing sounds like a Pete thing.
I hadn't until then changed fonts in Arch, so I was surprised it wasn't a more widely encountered issue.
Here's someone else encountering a similar issue on 7th September - I can't remember when I had the issue but it was definitely longer ago than that - long enough that it either happened again or was left unfixed for a month or two. (Actually I think I vaguely remember seeing something like because a configuration change could solve it, the problem wasn't going to be fixed, but I can't be 100% certain my memory isn't conflating it with some other issue.)
I am writing this after seeing someone else post the *exact* same problem, though he got no good answer and I can't find his post anymore (thought it was in the last few days). Ever since a full system update (pacman -Syu) a while ago, many fonts in Firefox, Chrome, and other programs are totally unreadable. They show up as gibberish, like wingdings font. With such a disastrous problem I would have expected Google to provide quick answers, but no such luck.
> The second thing has happened like twice so fuck you.
Gee, I must have missed it the first time round. :P
> there's no reason not to keep your system up to date and lots of good reasons to do so.
What's the benefit from upgrading from Firefox 48.0.1 to 48.0.2 ?
> Updated software, when *everything* is updated so you don't have to have your maintainers kludge between the version mismatches, has fewer bugs.
You're ignoring the fact that lots of software developers regularly add new bugsfeatures and make unnecessary changes for the sake of it.
I don't care if there are less bugs if it means something has stopped working how I need it to work - my issue is less with the nature of Arch and more with the current attitude of developers, but that's a whole nother rant I don't have time for. |