[feisty] Bad fonts with the latest Feisty upgrade

See the attached screenshot. The top window is a Konsole window opened before the upgrade, the second one after the upgrade.

I can confirm this after today's upgrade. I suspect it is caused by this upgrade:
https://launchpad.net/ubuntu/feisty/+source/fontconfig/2.4.2-1ubuntu1

Check for anti-alaising in your Fonts setting in System Setting. Unapplying
them, then applying them again might help, this seems to be very similar to
an error I had when I updated to Edgy. Let me know if this helps.

Check for anti-alaising in your Fonts setting in System Setting. Unapplying them, then applying them again might help, this seems to be very similar to an error I had when I updated to Edgy. Let me know if this helps.

Freddy, your suggestions has not helped in my case. The fonts are still blurred.

Just a quick "me too".
I noticed the same behaviour. The fonts in Gnome are basically the same as before, the KDE fonts got blurry and the fonts in Thunderbird/Firefox have changed too (to the worse).
Installing the attached .fonts.conf file helped a bit to make the KDE fonts a little bit more crisp and readable, still they are different than before.
What's even worse is, that Firefox/Thunderbird don't seem to respect the settings in .fonts.conf.
Please see the attached screenshot. Take the word "Datei", it's rendered differently in Firefox, Kate and gedit.

Clean install of Kubutnu Herd2 is not that bad, but I have noticed that it uses "Sans Serif" font as default. I had old user from Dapper times, so my fonts were Deja Vu, which seems to have rendering issue with latest fontconfig update.

I've changed all my fonts from "Sans Serif" to "DejaVu Sans" and they look as good as the fonts in Edgy.

The problem, which can be described as wrong font anti-aliasing with color-bleeding happened to me in a system upgraded from edgy to feisty. Wiping the partition clean and installing yesterday's feisty daily alternate snapshot created a fully woking desktop environment with proper font anti-aliasing.

I've this hunch that fontconfig and fontconfig-config were not upgraded cleanly but it could also be a problem with pango/cairo (yet, amarok does not do pango, now does it?); it could also be that the X server upgrade wasn't done cleanly and old libraries were not updated where they should have.

If it were a fontconfig problem I could not see what could have gone wrong apart from a bunch of files that were not removed from /etc/fonts/conf.d and that were moved to /etc/fonts/conf.avail in the newer fontconfig-config packaging. But having no symlinks to numbered names, they are merely trashy files.

Fixed with latest qt-x11 upload