Fonts look blurry if ~/.fonts.conf (even empty one) is present

Bug #69091 reported by Frank Siegert on 2006-10-29
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
fontconfig (Ubuntu)
Low
Unassigned

Bug Description

After a default Kubuntu installation, fonts look nicely anti-aliased and still clear (see attachment clear-before-appearance.png). But if I add a ~/.fonts.conf (and log out and in), they get completely blurry (see blurry-after-appearance.png), even if the ~/.fonts.conf is empty between <fontconfig> </fontconfig>. This caught me, because the Kubuntu system settings created a ~/.fonts.conf when I viewed the Appearance section (see the bug #69085).

If you think it is a mistake to have a quasi empty ~/.fonts.conf present, or the one that Kubuntu System Settings writes out is wrong (see linked bug: fonts.diff), then this bug against fontconfig may be rejected. But I assume, that if one setting is not present in ~/.fonts.conf, it is taken from /etc/fonts/fonts.conf, so an "empty" ~/.fonts.conf should not hurt.

This bug seems to have been encountered by various users who have added their information to #63403. Especially comment 20 explains this, and the following comments also conclude, that maybe for mentioned case (3) there should be a separate bug filed. Maybe my bug report fulfills this need.

Frank Siegert (fsiegert) wrote :
description: updated
Xavier (chantry-xavier) wrote :

The issue you describe here is even more odd. I don't understand why an empty ~/.fonts.conf makes any difference, there are no conflicts in this case.
The problem I was talking about is that it's not clear what the priority is between Xft resources and the settings in ~/.fonts.conf . If both conflict (eg having the Xft.hintstyle=hintmedium resources, and setting hintstyle to hintfull in ~/.fonts.conf), then a priority should be clearly made, and every apps should follow it.

Daniel Musketa (daniel-musketa) wrote :

I can reproduce this behavior (on Edgy).

Simon Edwards (simon-simonzone) wrote :

I seem to have the same problem on Gutsy. With ~/.fonts.conf present I always get super-blurry over-antialiased fonts. I've removed .fonts.conf and now my KDE4 fonts are good (slightly antialised), but my KDE3 fonts, Thunderbird, Firefox, & GIMP GUI are blurry.

PJSingh5000 (pjsingh5000) wrote :

I am experiencing this problem in Hardy. The systemsettings | Appearance option creates a local ~/.fonts.conf file. The settings in this file do not correspond to the options I select when I execute:
$ sudo dpkg-reconfigure fontconfig-config --force
   Select:
       Font tuning method for screen: Autohinter
       Enable subpixel rendering for screen: Automatic
       Enable bitmapped fonts by default? No
As a result the fonts revert to a fuzzy appearance. To correct this, I have to manually delete the local ~/.fonts.conf each time I access the Appearance option from systemsettings.

jjos (jbenjos) wrote :

Bug has been confirmed by multiple people. Changing status to Confirmed.

Changed in fontconfig:
status: New → Confirmed
GaryW (gnubyexample) wrote :

The bug report seems to mention two issues - (1) fuzzy fonts (2) undesirable creation of ~/.fonts.conf

The (2) bit of this issue that referred to system settings | Appearance creating ~/.fonts.conf each time it is accessed may now not exist in Intrepid.

$ cat /etc/lsb-release;date;uname -a;cd ~;find . -type f -name '.font*'
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION="Ubuntu 8.10"
Sat Feb 14 14:10:47 GMT 2009
Linux d183z2g 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux
./GNUstep/Library/WindowMaker/.fonts_converted
#The line above is just because I use WindowMaker so should be ignored.

I have accessed system settings | Appearance twice this morning and Intrepid seems not to have the undesirable behaviour of creating ~/.fonts.conf just because
you accessed system settings | Appearance

What follows is guesswork regarding why Intrepid Gnome no longer feels the need to create ~/.fonts.conf

useri@d183z2g:~$ grep issing /etc/fonts/conf.d/*.conf
/etc/fonts/conf.d/50-user.conf: <include ignore_missing="yes">~/.fonts.conf</include>
/etc/fonts/conf.d/51-local.conf: <include ignore_missing="yes">local.conf</include>
/etc/fonts/conf.d/52-languageselector.conf: <include ignore_missing="yes">language-selector.conf</include>

Gnome version in Intrepid is 2.24 according to this link
http://arstechnica.com/open-source/news/2008/10/ubuntu-gets-horny-intrepid-ibex-8-10-officially-released.ars

$ dpkg -l | grep gnome-control-center
ii gnome-control-center 1:2.24.0.1-0ubuntu7 utilities to configure the GNOME desktop

It might be that Gnome itself has been reworked to treat the presence of ~/.fonts.conf
as being now entirely optional. A Gnome expert might be able to confirm this.

Frank Siegert (fsiegert) wrote :

Hi garyuu,

Sorry, if that wasn't clear, but this report mentioned Kubuntu's System Settings, i.e. the KDE ones, but nonetheless, issue (2) is mainly discussed in #69085. Opening System Settings -- Appearance -- Fonts still creates a ".fonts.conf", even in Kubuntu 8.10 (KDE 4.1). I don't have the same hardware anymore, so I can't test, whether an empty .fonts.conf makes fonts blurry anymore (and that's what this bug report is mainly about). I only know that with my current hardware, fonts get better, if I change the KDE created defaults in .fonts.conf from rgba:none->rgb and hintstyle:hintmedium->hintfull.

Thanks,
Frank

GaryW (gnubyexample) wrote :

Hi Frank,

firstly apologies for not clicking through to #69085 when I first read this bug report.

the behaviour on my system is not an empty ~/.fonts.conf but a populated file in xml format.

In my 8.10 (KDE 4.1) setup a 23 line ~/.fonts.conf file is generated just by opening the
'appearance' tab of systemsettings (KDE)

https://answers.launchpad.net/ubuntu/+source/kdebase-workspace/+question/61092

If the question above is answered then then this bug report goes back to being a question
regarding fuzzy fonts rather than being also clouded by fonts.conf stuff.

Regards,
Gary.

Gen2ly (toddrpartridge) wrote :

Hmm, why hasn't this been reported upstream? Probably help get it fixed faster ;)

https://bugs.kde.org/show_bug.cgi?id=209841

Frank Siegert (fsiegert) wrote :

Hi Todd,

I think that this is the wrong Launchpad bug report to link to (it is assigned to fontconfig). You probably meant that one: https://bugs.launchpad.net/kdebase/+bug/69085 where I have now added your upstream bug watch.

To answer your question: Back when I reported it, this was still in KDE3 and the system settings module wasn't part of upstream KDE.

Frank

PJSingh5000 (pjsingh5000) wrote :

I no longer experience this issue in Kubuntu lucid Lynx 10.04 x64.

Victor Vargas (kamus) wrote :

@Frank, please could you check if this issue is still affecting you under latest release included in Kubuntu 10.04? Thanks!

Changed in fontconfig (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Craig Magina (craig.magina) wrote :

I experienced this in Kubuntu 11.04 amd64 fully updated as of 01/31/2011. I opened the font configuration screen, did not change anything, did not apply any changes nor was I asked to and then logged out and back in to find my fonts were no longer anti-aliased, etc. I deleted the .fonts.conf file and .fontsconfig directory and then logged out and back in to find my fonts returned to the what they were prior to opening the font config screen.

Marking back to Confirmed on Craig Mangina's test.

Changed in fontconfig (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers