fontconfig-config 45-latin.conf and ~/.fonts.conf overriden by new 60-latin.conf

Bug #387848 reported by zzz on 2009-06-16
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
fontconfig (Debian)
New
Unknown
fontconfig (Ubuntu)
High
Unassigned
Nominated for Karmic by andrey i. mavlyanov
Nominated for Lucid by zzz
Nominated for Maverick by zzz

Bug Description

Binary package hint: fontconfig

We seem to have clashing /etc/fonts/conf.d/45-latin.conf vs /etc/fonts/conf.d/60-latin.conf on karmic in fontconfig-config 2.6.0-1ubuntu12.

These a) use different methods of aliasing fonts to their default families and b) have different choices for the default fonts. Currently 60-latin.conf is the one always taking effect.

In addition, 60-latin.conf is now overriding 50-user.conf and 51-local.conf, thus preventing user customisation of their aliased fonts from working. e.g., I have a ~/.fonts.conf that sets my own preferred font for the monospace family. This is no longer working on karmic

One of these latin.confs should be removed and the remaining one kept at 45-latin.conf

ProblemType: Bug
Architecture: i386
Date: Tue Jun 16 13:08:22 2009
DistroRelease: Ubuntu 9.10
Package: fontconfig-config 2.6.0-1ubuntu12
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.30-9.10-generic
SourcePackage: fontconfig
Uname: Linux 2.6.30-9-generic i686

zzz (oldman-deactivatedaccount) wrote :
Alexander Sack (asac) wrote :

arne, do we want the 45-latin or 60-latin thing to be used (disregard the number for now).

Changed in fontconfig (Ubuntu):
assignee: nobody → Alexander Sack (asac)
importance: Undecided → High
status: New → In Progress
zzz (oldman-deactivatedaccount) wrote :

is there anything more I can do to help progress this bug?

Alexander Sack (asac) wrote :

in conf.d README, the following is said about the priorities:

Files begining with: Contain:

 00 through 09 Font directories
 10 through 19 system rendering defaults (AA, etc)
 20 through 29 font rendering options
 30 through 39 family substitution
 40 through 49 generic identification, map family->generic
 50 through 59 alternate config file loading
 60 through 69 generic aliases, map generic->family
 70 through 79 select font (adjust which fonts are available)
 80 through 89 match target="scan" (modify scanned patterns)
 90 through 99 font synthesis

Isnt that scheme used properly for *-latin.conf ?

Peng Deng (d6g) wrote :

I can confirm this problem with the latest karmic daily build (Aug 23).

On jaunty, I also have 60-latin.conf enabled by default but my own ~/.fonts.conf works without any problem.

And the contents of 60-latin.conf on jaunty and on karmic are completely the same.

Confirming the problem. Can't override latin and non-latin via ~/.font.conf or /etc/fonts/local.conf due to 60-latin.conf and 65-nonlatin.conf

please fix this before 9.10 release!

Workaround:

$ cd /etc/fonts/conf.d/
$ sudo mv 50-local.conf 05-local.conf
$ sudo mv 50-user.conf 05-user.conf

Crux (crux) wrote :

Confirming the problem as well. I miss being able to remove smoothing from a few tiny fonts. :'(

Andrey's workaround solved it (at least until the next update), but I would really like to see this fixed.

zzz (oldman-deactivatedaccount) wrote :

any further update on this bug and what might happen for maverick? its been sitting around marked as 'in progress' for a while now :-)

another 3 months have gone by without any activity? should I unassign this and put it back to 'confirmed' if nobody is actively working on it?

Martin Pitt (pitti) on 2011-01-07
Changed in fontconfig (Ubuntu):
status: In Progress → Triaged
assignee: Alexander Sack (asac) → nobody
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Martin Pitt (pitti) wrote :

I'll unassign this one and instead forward it to Debian, as this affects them as well.

Changed in fontconfig (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
Changed in fontconfig (Debian):
status: Unknown → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.