Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#4963 - fontconfig sometimes requires a reinstall for fonts to work properly
Attached to Project:
Arch Linux
Opened by name withheld (Gullible Jones) - Wednesday, 05 July 2006, 03:11 GMT
Opened by name withheld (Gullible Jones) - Wednesday, 05 July 2006, 03:11 GMT
|
DetailsThere's some mighty weird stuff going on with fontconfig right now, which seems to be dependent on the presence of other packages. Here is what happens in four different types of desktop environments.
On Xfce4-SVN: if fontconfig is not reinstalled after its first installation, antialiasing doesn't work, fonts look very bad (chunky and distorted), and bitmap fonts are not registered even if specifically enabled. After reinstalling fontconfig, everything is as it should be. On Gnome and GTK-based DIY environments (e.g. FVWM + ROX): antialiasing works right, and fonts look fine, but bitmap fonts are still unusable even when enabled. Again, reinstalling fontconfig fixes this. On KDE: No AA problems, bitmap fonts work fine to begin with if enabled. No reinstall is required. Running fc-cache or ldconfig as root (as specified in the fontconfig install script) doesn't seem to help, which makes me think that this might be a case of some GTK-related package(s) messing things up. |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 05 July 2006, 06:05 GMT
Reason for closing: Duplicate
Additional comments about closing: Please don't open many bugs about the same item, take a look at 4712, which is also opened by you.
Wednesday, 05 July 2006, 06:05 GMT
Reason for closing: Duplicate
Additional comments about closing: Please don't open many bugs about the same item, take a look at 4712, which is also opened by you.