Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

The fonts are not shown correctly, they are smaller than normal.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

thing more Ask the installation, deleting files essential to Windows fonts
and dejavu

   * What was the outcome of this action?

Fonts smaller and less anti-aliasing

   * What outcome did you expect instead?

The same fonts and display the version 2.9.0.7-1. : (

Files changes:

~/.fonts.config at ~/.config/fonts/fonts.config
~/.fontconfig at ~/.cache/fontconfig
~/.fonts at ~/.local/share/fonts

And creates links this directories.

File fonts.conf:

<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
 <match target="font">
  <edit mode="assign" name="rgba">
   <const>rgb</const>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="hinting">
   <bool>true</bool>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="hintstyle">
   <const>hintfull</const>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="antialias">
   <bool>true</bool>
  </edit>
 </match>
</fontconfig>

*** End of the template - remove these lines ***

I have put the file ~/.fonts.conf at ~/.config/fontconfig/fonts.conf

Then does not result.

The fonts appear as Liberation.

No solution or we have to wait for 2.11.0?

I see no other.

Facebook looks terrible now. Must be due to 714279.

# dpkg -i libfontconfig1_2.9.0-7.1_i386.deb fontconfig_2.9.0-7.1_i386.deb fontconfig-config_2.9.0-7.1_all.deb
Fixed it. Thank God!

But now
The following packages have unmet dependencies:
 openjdk-7-jre : Depends: libfontconfig1 (>= 2.10.0) but 2.9.0-7.1 is installed and it is kept back.
 libgtk-3-bin : Depends: libfontconfig1 (>= 2.10.0) but 2.9.0-7.1 is installed and it is kept back.
 emacs-snapshot : Depends: libfontconfig1 (>= 2.10.0) but 2.9.0-7.1 is installed and it is kept back.

And on and on.

What am I supposed to do?

Never install another package again?

Facebook looks terrible now. Must be due to 714279.

# dpkg -i libfontconfig1_2.9.0-7.1_i386.deb fontconfig_2.9.0-7.1_i386.deb fontconfig-config_2.9.0-7.1_all.deb
Fixed it. Thank God!

But now
The following packages have unmet dependencies:
 openjdk-7-jre : Depends: libfontconfig1 (>= 2.10.0) but 2.9.0-7.1 is installed and it is kept back.
 libgtk-3-bin : Depends: libfontconfig1 (>= 2.10.0) but 2.9.0-7.1 is installed and it is kept back.
 emacs-snapshot : Depends: libfontconfig1 (>= 2.10.0) but 2.9.0-7.1 is installed and it is kept back.

And on and on.

What am I supposed to do?

Never install another package again?

severity 714279 serious
notfound 714279 2.9.0-7.1
thanks

I can confirm that something goes wrong after upgrading fontconfig,
and that really has to get fixed.

cu
Adrian

I encountered the same problems.  By fiddling some configuration bits, I was
able to restore the previous "good" font rendering:

1. Fix the symlink for /etc/fonts/conf.d/11-lcdfilter-default.conf (it was
pointing to /etc/fonts/conf.avail/, but the file is now in
/usr/share/fontconfig/conf.avail/.

2. Change "append" back to "assign" in contradiction to the comments in
10-autohint.conf, 10-subpixel-rgb.conf, and 11-lcdfilter-default.conf.

3. Run fc-cache -f and restart apps to get new configuration to be fully
active.

I can confirm Matthew's fix is working for me.

I didn't have 11-lcdfilter-default.conf nor 10-subpixel-rgb.conf linked
or enabled, so all I needed to do is change "append" to "assign" in
10-autohint.conf to get back to font rendering that didn't make my eyes
spontaneously self-combust.

My eyes thank you Matthew,

Hi:

Solve in file ~/.config/fontconfig/fonts.conf, in the section 'hintstyle',
change to 'hintslight'.

No problem. :-) The vision is correct before. :)

Close. Solved.

reopen 714279
thanks


Please don't close this bug (even when you are the original reporter)
only because you managed to find a workaround.

This issue has to be fixed in a way that no user will run into it in the
future after an upgrade.

cu
Adrian

El 17/07/13 19:20, Adrian Bunk escribió:

Ok. Sorry.

control: severity -1 important

This is a non-severe issue and has a straightforward workaround.

Best wishes,
Mike

severity 714279 serious
thanks

Hi Michael,

it sounds like a joke that you wrote "This is a non-severe issue".

Many people had a real WTF? experience after upgrading to the broken
package, and this is an issue that negatively effects a huge number
of GUI applications.

By lowering the severity you imply that it would be OK if the bug still
exists when jessie becomes stable - and in reality that would be an
absolute disaster.

The simplicity of the workarounds implies that it should be easy to fix,
not that every single user should have to do the workaround himself.

cu
Adrian

In that case, version 2.9.0-7.1 had serious problems too. See

http://lists.debian.org/debian-user/2012/05/msg02439.html
http://lists.debian.org/debian-user/2012/05/msg02534.html

and a few days later, I also had to disable the Times font, which
was too small.

That looks completely unrelated.

#714279 is a regression in 2.10, and looking at the workaround this bug
here is mostly about a confusion on whether "append" or "assign" is
correct in configuration files.

Whatever causes your problems in 2.9.0-7.1 looks completely unrelated,
please don't create confusion by discussing that here in the #714279 bug.

cu
Adrian

severity 714279 important
thanks

This bug happens only when people have fiddled with non-trivial parts of
the fontconfig configuration. I agree it should be fixed in an ideal
world, but I fail to see how this qualifies as “serious”. Please point
me to the relevant part of the policy if you feel this is incorrect.

Cheers,

The statement in your first sentence is wrong - running into this bug
does not require manual fiddling with fontconfig configuration as you
claim.


Quoting the workaround in the bug log:

<--  snip  -->

2. Change "append" back to "assign" in contradiction to the comments in
10-autohint.conf, 10-subpixel-rgb.conf, and 11-lcdfilter-default.conf.

<--  snip  -->


10-autohint.conf and 11-lcdfilter-default.conf are shipped as part of
fontconfig-config, and this problem is present there.


And this workaround is basically a revert of upstream
commit 1aaf8b77 (Bug 17722 - Don't overwrite user's
configurations in default config).


I am using FVWM, and after looking at this commit I'd guess people using
one of the major desktop environments might not run into this problem.

cu
Adrian

The files in conf.avail/ (symlinked in conf.d/) are there for system
wide configuration. The use of "append" there is right, because that
leaves the choice to each user to change their config, if they want
(using "assign" in ~/.config/fontconfig/fonts.conf ).
The problem arises because fonts options in the desktop environment
usually override the default fontconfig configuration, even if you
don't touch any fonts setting in the DE.
For example Gnome3 default config enable the autohinter and set the
hintstyle to "full". If you enable subpixel hinting in conf.d/ you
will get a fuzzy result, because autohinter is not designed to work
with subpixel (the subpixel setting is not override because Gnome3
defaults doesn't touch this option).
The best thing to do is to set the DE fonts settings to be equal to
the conf.d/ settings and/or the user's settings (in Gnome3 you can
change settings with gnome-tweak-tool), because DE fonts settings will
have always the highest priority, at least on Xfce where I'm testing
it.
BTW it looks like Gnome and Xfce (and maybe others) uses Xft, that
have priority on fontconfig: maybe the bug should be reported to the
DEs teams to make them use fontconfig instead of Xft?