raj967452 / googlefontdirectory

Automatically exported from code.google.com/p/googlefontdirectory
0 stars 0 forks source link

Fira Sans blank on certain Linux-based setups #368

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Use Firefox (or Iceweasel) 33+ on Linux (Debian Sid, Gentoo, Knoppix, and 
Mint have been mentioned by our users)
2. Navigate to http://www.google.com/fonts/specimen/Fira+Sans

What is the expected output? What do you see instead?
I expect to see the characters for all rendered in the browser. Instead, only 
Light 300 Italic is rendering and everything else is blank (not replaced by a 
fallback font, either).

What version of the product are you using? On what operating system?
Firefox 33.0 and Iceweasel 34 for Linux.

Please provide any additional information below.
I've walked through disabling extra add-ons in Firefox (in case they were 
blocking the rendering) and there is no change.

Original issue reported on code.google.com by Cassidy....@gmail.com on 21 Nov 2014 at 4:28

Attachments:

GoogleCodeExporter commented 9 years ago
Iceweasel 31.2.0 (esr release) is also affected.

Another thing I noticed that loading the referenced page takes > 10 secs of 
100% CPU utilization on 1 core of an AMD Phenom II X4 B55 Processor (3.2 GHz)

Original comment by Diederik...@gmail.com on 21 Nov 2014 at 5:12

GoogleCodeExporter commented 9 years ago
Users are reporting the font working when it's hosted elsewhere (i.e. on 
http://mozilla.github.io/Fira/), so it sounds like it's either an old version 
on Google or some other issue specific to the version Google is hosting.

Original comment by Cassidy....@gmail.com on 21 Nov 2014 at 5:25

GoogleCodeExporter commented 9 years ago
Another user has reported the same issue (Fira Sans not rendering at all on our 
site, System76.com), except this time it's in Chrome. :o Other fonts render 
fine; it's just Fira Sans that has the issue.

Attached are screenshots of the issue showing in Chrome on the Google font 
directory.

Original comment by Cassidy....@gmail.com on 21 Nov 2014 at 6:53

Attachments:

GoogleCodeExporter commented 9 years ago
It is also worth noting that the issue above was in Windows, not Linux. So it 
could be a network configuration (proxy?) issue rather than tied directly to 
the OS or browser.

Original comment by Cassidy....@gmail.com on 21 Nov 2014 at 6:54

GoogleCodeExporter commented 9 years ago
After more testing, I am able to reproduce it here every time in Google Chrome 
Beta 64-bit on both Ubuntu 14.04 and Ubuntu 14.10. I have yet to reproduce it 
in Chrome Stable on Ubuntu.

Original comment by Cassidy....@gmail.com on 3 Dec 2014 at 12:04

GoogleCodeExporter commented 9 years ago
Same here with Chromium (Version 39.0.2171.71 (64-bit)) on Arch Linux. No proxy 
setup but i do have both IPv4 and IPv6.

Original comment by slave...@gmail.com on 8 Dec 2014 at 7:08

Attachments:

GoogleCodeExporter commented 9 years ago
Hello,

I also saw this Issue on the http://rust-lang.org website running Firefox 33/34 
and  on x86-64 Archlinux.  Screenshots and other reports were documented in the 
issue at: https://github.com/rust-lang/rust/issues/19257#issuecomment-67077954 
.  The fixes found were to install the otf-fira-sans and otf-fira-mono AUR 
packages or to remove the Fira TTF fonts installed from the 
ttf-google-fonts-git repo.

Original comment by bbr...@gmail.com on 16 Dec 2014 at 5:22

GoogleCodeExporter commented 9 years ago
i can confirm the issue on both iceweasel (firefox) and chromium (chrome) on 
linux.

no network error. the area where the text should be shown is white. no chance 
to select the text.

including the ones from mozilla works here, too.

Original comment by rimo...@gmail.com on 20 Feb 2015 at 8:04

GoogleCodeExporter commented 9 years ago
Confirmed (and really annoying) on Firefox 36.0.1 on Arch Linux 64-bit. (I have 
IPv6 disabled.) Does not appear in Firefox 36.0.1 on a virtualized Windows XP 
from the same box.

Original comment by mdu...@gmail.com on 18 Mar 2015 at 7:50