I always love websites with custom fonts that don't render correctly. When I see a website with great typography, most of the time it turns out to be Georgia or Arial, or sometimes even Timew New Roman (which his a good font, but simply overused). I've yet to see a custom font that reads better than correctly applied default fonts.
When a site like kernel.org goes online with a broken font, something must be fundamentally wrong in the world of programmers and people generating content for displays. What would be the situation like, if we were printing millions of books with 20 dpi technology? Would this be ignored by the masses and people who are annoyed by the eye-hurting results would be trolls?
We should see this as a clear (cough) signal, that it is time to start some major broken-font-campaign - more and more web developers seem to be so overloaded with CSS and JS framework learning, they totally forget about the most basic things - IMHO it is still the first and most noble duty of a real webdev to make a site nicely readable on all displays.
This annoying font-disease must be taken very seriously - it is ignoring the most important aspects of life: health. I feel offended if somebody forces me to read a website with such a broken font - it hurts my eyes, and as a computer guy I need my eyes for work, so it is a serious attack.
I was humbly accepting it as a personal disability for years, that I needed WinXP fonts on every Linux distro to have a satisfying font display. But I kept wondering about how the creators of thousands of Linux tutorial screenshots could not realize that they were looking at a broken font and destroying the functionality of their most important input devices.
Luckily in the last years it got much better on Linux, but then came the iFlood, Win7, and finally the ultimate weapon of ophthalmologists for generating an endless income stream: webfonts.
Now I am confronted every single day with websites with broken fonts. This is a serious regression and every web designer and every programmer involved in font rendering code should stop working on anything else until this problem is fixed.
Yes, I know there are many reasons for this problem, it is not only the web developers - anyway, please let us fix it now.
Google Chrome on Linux Mint 13 (Ubuntu 12.04LTS). Probably same issue on Chrome on Windows 7.
The reason I didn't mention my hardware at first is because nobody ever gives a damn about typography. I've tested these bugs cross-platform often enough, but nobody ever replies, so I stopped doing that.
I knew these kind of answers would pop up, I had one sentence predicting this in my text, but erased it to let the magic happen.
Are you able to realize that it is, of many options you have, the dumbest possibility to just burp a simple "it works here". Would you answer this on a bugreport?
I assume, it was an ironic answer, in this case I congrat you for holding the mastership of the highest art of subtile trolling, very inspriring.
In fact you are simulating the typical xtreme-dumb answers perfectly, that are received on "bad-font-whining" regularly - this is exactly the reason why we need a major bad-font-campaign, because this is not only a technical problem, but the roots seem to be hidden in a deeper socio-techno-cultural level of our brains - that "systems are getting too complex"-stuff leads in the end to the human brain regressing strongly in certain areas to amoeba-state.
If I was unable reproduce the bug with the information given, it seems reasonable to mention that. Also, the effort required by the bug reporter to mention basic information on the setup they use is much less than for a web developer to boot up 5 different systems (including iOS and Android) to test out each major browser in them.
I'll have you know that I have been wary of using non-default fonts because of these reports.