View previous topic :: View next topic |
Author |
Message |
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Sun Feb 23, 2014 2:31 pm Post subject: [SOLVED] Chromium 33.0.1750.117 has jagged fonts |
|
|
My newest version of the Google chromium browser, 33.0.1750.117, has jagged fonts, similar to here.
I'm using KDE and have tried all combinations of its Use anti-aliasing settings. I don't believe the previous version of chromium had this problem.
Any hints to fixing this would be gratefully received.
[SOLVED] lrbb, below, has an extension which substitutes Arial for Helvetica. Also, astroe, below, has a fontconfig setting which also solves the problem. [/SOLVED]
Last edited by cfgauss on Sun Mar 16, 2014 8:21 pm; edited 7 times in total |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10589 Location: Somewhere over Atlanta, Georgia
|
Posted: Sun Feb 23, 2014 3:04 pm Post subject: |
|
|
I say yuck to both. See Getting Beautiful Fonts in Gentoo.
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
dehpeh n00b
Joined: 19 Dec 2002 Posts: 15 Location: Germany
|
Posted: Mon Feb 24, 2014 12:15 pm Post subject: |
|
|
Same font-problem here with Chromium 33.0.1750.117 (Gnome 2.32.1)
Solved, solution:
Code: | eselect fontconfig enable 70-no-bitmaps.conf |
and if enabled:
Code: | eselect fontconfig disable 70-yes-bitmaps.conf |
Last edited by dehpeh on Wed Mar 12, 2014 5:58 pm; edited 2 times in total |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Mon Feb 24, 2014 3:37 pm Post subject: |
|
|
Just checking into this thread. Upgraded from Chromium 27 to 33 over the weekend. Horrible fonts all around! The UI fonts stink (small tab titles and large URL font), which from what I understand is the fault of Google, who has hard coded in these sizes into the source. But, I can deal with that.
Even worse is the horrible web font rendering, as shown by the above links. I tried switching everything to the Bitstream fonts, which I use in Firefox, but it didn't change a thing. Something seems broken in version 33.
I'm downgrading to version 32, and hoping it will get sorted out.
EDIT
Downgrading to version 32 does solve the font rendering issues. And a tip for those downgrading... rename or remove the file "~/.config/chromium/Default/ Web Data", else you will receive a warning each time you launch the browser that the profile was created with a newer version. |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10589 Location: Somewhere over Atlanta, Georgia
|
Posted: Mon Feb 24, 2014 5:54 pm Post subject: |
|
|
This is very curious because chromium-33.0.1750.117 renders beautiful fonts on my machine. I had thought that the reason was that there were other setup-related issues on the OP's machine.
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Mon Feb 24, 2014 6:39 pm Post subject: |
|
|
John R. Graham wrote: | This is very curious because chromium-33.0.1750.117 renders beautiful fonts on my machine. I had thought that the reason was that there were other setup-related issues on the OP's machine. | Perhaps it is a configuration issue. Can you post your `eselect fontconfig list`?
This is what mine looks like. I have some of the options turned off that are recommended in the link you posted above, but for testing earlier I enabled everything in the Gentoo Beautiful Fonts guide, and still had bad webfonts.
Code: | Available fontconfig .conf files (* is enabled):
[1] 10-autohint.conf
[2] 10-no-sub-pixel.conf
[3] 10-scale-bitmap-fonts.conf *
[4] 10-sub-pixel-bgr.conf
[5] 10-sub-pixel-rgb.conf
[6] 10-sub-pixel-vbgr.conf
[7] 10-sub-pixel-vrgb.conf
[8] 10-unhinted.conf
[9] 11-lcdfilter-default.conf
[10] 11-lcdfilter-legacy.conf
[11] 11-lcdfilter-light.conf
[12] 20-unhint-small-dejavu-sans-mono.conf
[13] 20-unhint-small-dejavu-sans.conf
[14] 20-unhint-small-dejavu-serif.conf
[15] 20-unhint-small-vera.conf *
[16] 25-unhint-nonlatin.conf
[17] 30-metric-aliases.conf *
[18] 30-urw-aliases.conf *
[19] 40-nonlatin.conf *
[20] 42-luxi-mono.conf *
[21] 45-latin.conf *
[22] 49-sansserif.conf *
[23] 50-user.conf *
[24] 51-local.conf *
[25] 57-dejavu-sans-mono.conf
[26] 57-dejavu-sans.conf
[27] 57-dejavu-serif.conf
[28] 59-google-droid-sans-mono.conf
[29] 59-google-droid-sans.conf
[30] 59-google-droid-serif.conf
[31] 60-latin.conf *
[32] 60-liberation.conf
[33] 65-fonts-persian.conf *
[34] 65-khmer.conf
[35] 65-nonlatin.conf *
[36] 69-unifont.conf *
[37] 70-no-bitmaps.conf
[38] 70-yes-bitmaps.conf
[39] 80-delicious.conf *
[40] 90-synthetic.conf *
[41] 99pdftoopvp.conf
|
One thing I noticed after my recent update was a line saying ~/.fonts.conf is deprecated now. I do have this file. Looks like the last time I edited it was back in 2008. Perhaps this could also be the culprit.... Although I tested with another user, without a .fonts.conf, and the results look the same. |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10589 Location: Somewhere over Atlanta, Georgia
|
Posted: Mon Feb 24, 2014 6:47 pm Post subject: |
|
|
Code: | IPSN-JOHNGRAH2 ~ $ sudo eselect fontconfig list
Available fontconfig .conf files (* is enabled):
[1] 10-autohint.conf *
[2] 10-no-sub-pixel.conf
[3] 10-scale-bitmap-fonts.conf *
[4] 10-sub-pixel-bgr.conf
[5] 10-sub-pixel-rgb.conf *
[6] 10-sub-pixel-vbgr.conf
[7] 10-sub-pixel-vrgb.conf
[8] 10-unhinted.conf
[9] 11-lcdfilter-default.conf
[10] 11-lcdfilter-legacy.conf
[11] 11-lcdfilter-light.conf
[12] 20-unhint-small-dejavu-sans.conf *
[13] 20-unhint-small-dejavu-sans-mono.conf *
[14] 20-unhint-small-dejavu-serif.conf *
[15] 20-unhint-small-vera.conf *
[16] 25-unhint-nonlatin.conf *
[17] 30-metric-aliases.conf *
[18] 30-urw-aliases.conf *
[19] 40-nonlatin.conf *
[20] 42-luxi-mono.conf *
[21] 45-latin.conf *
[22] 49-sansserif.conf *
[23] 50-user.conf *
[24] 51-local.conf *
[25] 57-dejavu-sans.conf *
[26] 57-dejavu-sans-mono.conf *
[27] 57-dejavu-serif.conf *
[28] 60-latin.conf *
[29] 60-liberation.conf
[30] 65-fonts-persian.conf *
[31] 65-khmer.conf
[32] 65-nonlatin.conf *
[33] 69-unifont.conf *
[34] 70-no-bitmaps.conf
[35] 70-yes-bitmaps.conf
[36] 80-delicious.conf *
[37] 90-synthetic.conf *
[38] 99pdftoopvp.conf | I also have a ~/.fonts.conf file. I've seen the deprecation messages but not acted on them yet.
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
mani001 Guru
Joined: 04 Dec 2004 Posts: 485 Location: Oleiros
|
Posted: Mon Feb 24, 2014 7:25 pm Post subject: |
|
|
Same problem here...did anyone find a "real" solution? I'm thinking that maybe is related to the graphic drivers since I update chromium in two computers with different results. They both have nvidia cards, but one of them using nouveau (no problem here), while the one using nvidia-drivers is showing the ugly fonts.... Regarding the latter, it's using the legacy nvidia-drivers (304.119) since the graphics card is really old...
Cheers!! |
|
Back to top |
|
|
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Mon Feb 24, 2014 7:54 pm Post subject: |
|
|
mani001 wrote: | They both have nvidia cards, but one of them using nouveau (no problem here), while the one using nvidia-drivers is showing the ugly fonts.... Regarding the latter, it's using the legacy nvidia-drivers (304.119) since the graphics card is really old... |
My box is using nvidia-drivers-334.16-r7, the latest unstable release in portage. And I have the bad Web fonts described by others.
Since chromium takes so long to emerge, is there any way to emerge two versions: a working version 32.0.1700.107 and a testing version, say 33.0.1750.117, for which parameters could be varied? |
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Mon Feb 24, 2014 10:26 pm Post subject: |
|
|
cfgauss wrote: | Since chromium takes so long to emerge, is there any way to emerge two versions: a working version 32.0.1700.107 and a testing version, say 33.0.1750.117, for which parameters could be varied? | Use quickpkg to create a binary of chromium and then emerge with the -K option to select the binary instead of building from source.
I'm using the xf86-video-intel graphics drivers, so if it is a driver issue, it extends outside nVidia. |
|
Back to top |
|
|
mani001 Guru
Joined: 04 Dec 2004 Posts: 485 Location: Oleiros
|
|
Back to top |
|
|
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Tue Feb 25, 2014 1:14 pm Post subject: |
|
|
Thanks for the link but it didn't solve this problem. What worked is reverting to version 32.0.1700.107, which is still in portage. |
|
Back to top |
|
|
lrbb n00b
Joined: 13 Jan 2012 Posts: 3
|
Posted: Tue Feb 25, 2014 7:31 pm Post subject: |
|
|
I have no idea what's causing this, but the Helvetica font seems to be the only problem for me. Here's a little hack extension to load Arial instead of Helvetica, via CSS.
- make the following files in some empty directory
- go to chrome://extensions
- check the developer mode box
- Load unpacked extension
- point to the new directory
manifest.json
Code: | {
"name": "Fix Helvetica",
"description": "Fix Helvetica",
"version": "0.1",
"content_scripts": [ {
"css": [ "Custom.css" ],
"matches": [ "http://*/*", "https://*/*" ]
} ],
"manifest_version": 2
}
|
Custom.css
Code: | @font-face { font-family: 'Helvetica'; src: local('Arial')} |
Effects should take place immediately. Worked for me. Maybe some simpler way to do this, but this is the way it turned out. |
|
Back to top |
|
|
mani001 Guru
Joined: 04 Dec 2004 Posts: 485 Location: Oleiros
|
Posted: Tue Feb 25, 2014 8:56 pm Post subject: |
|
|
That did the trick for me too
Thank you very much lrbb!! |
|
Back to top |
|
|
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Wed Feb 26, 2014 1:58 am Post subject: |
|
|
lrbb wrote: | I have no idea what's causing this, but the Helvetica font seems to be the only problem for me. Here's a little hack extension to load Arial instead of Helvetica, via CSS. |
This worked for me, too. Many thanks. I wonder why this is a problem in chromium-33.0.1750-117 but not chromium-32.0.1700.107? |
|
Back to top |
|
|
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Wed Feb 26, 2014 7:34 pm Post subject: |
|
|
mikegpitt wrote: | cfgauss wrote: | Since chromium takes so long to emerge, is there any way to emerge two versions: a working version 32.0.1700.107 and a testing version, say 33.0.1750.117, for which parameters could be varied? | Use quickpkg to create a binary of chromium and then emerge with the -K option to select the binary instead of building from source. |
Many thanks for this very useful tip. |
|
Back to top |
|
|
jserink Veteran
Joined: 30 Jan 2004 Posts: 1008
|
Posted: Thu Feb 27, 2014 3:10 am Post subject: |
|
|
Brilliant!
WORKED HERE! |
|
Back to top |
|
|
astroe n00b
Joined: 12 Aug 2004 Posts: 14 Location: Bucharest, Romania
|
Posted: Thu Feb 27, 2014 1:37 pm Post subject: |
|
|
John R. Graham wrote: | Code: | IPSN-JOHNGRAH2 ~ $ sudo eselect fontconfig list
Available fontconfig .conf files (* is enabled):
[1] 10-autohint.conf *
[2] 10-no-sub-pixel.conf
[3] 10-scale-bitmap-fonts.conf *
[4] 10-sub-pixel-bgr.conf
[5] 10-sub-pixel-rgb.conf *
[6] 10-sub-pixel-vbgr.conf
[7] 10-sub-pixel-vrgb.conf
[8] 10-unhinted.conf
[9] 11-lcdfilter-default.conf
[10] 11-lcdfilter-legacy.conf
[11] 11-lcdfilter-light.conf
[12] 20-unhint-small-dejavu-sans.conf *
[13] 20-unhint-small-dejavu-sans-mono.conf *
[14] 20-unhint-small-dejavu-serif.conf *
[15] 20-unhint-small-vera.conf *
[16] 25-unhint-nonlatin.conf *
[17] 30-metric-aliases.conf *
[18] 30-urw-aliases.conf *
[19] 40-nonlatin.conf *
[20] 42-luxi-mono.conf *
[21] 45-latin.conf *
[22] 49-sansserif.conf *
[23] 50-user.conf *
[24] 51-local.conf *
[25] 57-dejavu-sans.conf *
[26] 57-dejavu-sans-mono.conf *
[27] 57-dejavu-serif.conf *
[28] 60-latin.conf *
[29] 60-liberation.conf
[30] 65-fonts-persian.conf *
[31] 65-khmer.conf
[32] 65-nonlatin.conf *
[33] 69-unifont.conf *
[34] 70-no-bitmaps.conf
[35] 70-yes-bitmaps.conf
[36] 80-delicious.conf *
[37] 90-synthetic.conf *
[38] 99pdftoopvp.conf | I also have a ~/.fonts.conf file. I've seen the deprecation messages but not acted on them yet.
- John |
John, having the same list of fontconfig .conf files as you, I managed to fix my Chromium 33 font display by running:
Code: | eselect fontconfig enable 70-no-bitmaps.conf |
|
|
Back to top |
|
|
mikegpitt Advocate
Joined: 22 May 2004 Posts: 3224
|
Posted: Thu Feb 27, 2014 7:40 pm Post subject: |
|
|
astroe wrote: | John, having the same list of fontconfig .conf files as you, I managed to fix my Chromium 33 font display by running:
Code: | eselect fontconfig enable 70-no-bitmaps.conf |
| Excellent! This also worked for me |
|
Back to top |
|
|
cfgauss l33t
Joined: 18 May 2005 Posts: 688 Location: USA
|
Posted: Fri Feb 28, 2014 11:16 pm Post subject: |
|
|
astroe wrote: | John, having the same list of fontconfig .conf files as you, I managed to fix my Chromium 33 font display by running:
Code: | eselect fontconfig enable 70-no-bitmaps.conf |
|
I originally used lrbb's extension (which fixed the problem). I then disabled the extension. Even though I have more fonts than John and even different enable/disable choices among the fonts I have in common with John, astroe's fix worked for me as well. Many thanks! |
|
Back to top |
|
|
$moke n00b
Joined: 10 May 2005 Posts: 17
|
Posted: Sat Mar 01, 2014 5:20 pm Post subject: |
|
|
mikegpitt wrote: | astroe wrote: | John, having the same list of fontconfig .conf files as you, I managed to fix my Chromium 33 font display by running:
Code: | eselect fontconfig enable 70-no-bitmaps.conf |
| Excellent! This also worked for me |
That worked for me also. Thanks! _________________ There is nothing that can`t be done with Linux, only if you know HOW!!! |
|
Back to top |
|
|
snake111 Tux's lil' helper
Joined: 18 Dec 2004 Posts: 117
|
Posted: Sat Mar 01, 2014 5:55 pm Post subject: |
|
|
mikegpitt wrote: | astroe wrote: | John, having the same list of fontconfig .conf files as you, I managed to fix my Chromium 33 font display by running:
Code: | eselect fontconfig enable 70-no-bitmaps.conf |
| Excellent! This also worked for me |
Same here, fixed! Thanks! |
|
Back to top |
|
|
caaarlos Apprentice
Joined: 27 Apr 2012 Posts: 155
|
Posted: Sat Mar 01, 2014 10:45 pm Post subject: |
|
|
Hello, Code: | eselect fontconfig enable 70-no-bitmaps.conf | does not woked for me. Only lrbb's solution works. |
|
Back to top |
|
|
toydarian n00b
Joined: 30 Oct 2013 Posts: 8
|
Posted: Mon Mar 03, 2014 10:04 am Post subject: |
|
|
astroe wrote: |
Code: | eselect fontconfig enable 70-no-bitmaps.conf |
|
fixed it! thank you! |
|
Back to top |
|
|
Pistos Apprentice
Joined: 29 Jul 2003 Posts: 175 Location: Canada
|
Posted: Mon Mar 03, 2014 8:04 pm Post subject: |
|
|
[quote="astroe"] John R. Graham wrote: | John, having the same list of fontconfig .conf files as you, I managed to fix my Chromium 33 font display by running:
Code: | eselect fontconfig enable 70-no-bitmaps.conf |
| This didn't work for me. I already had it enabled. Disabling and enabling again didn't change anything.
One thing has been clear to me for years: On Windows and OSX, fonts Just Work. On Linux, we have to painstakingly set things up "just right", and re-set things up now and again due to "new" problems like this one.
EDIT: Ah, I had to disable 70-yes-bitmaps.conf . |
|
Back to top |
|
|
|