You are not logged in.
Did a fresh install with latest packages, frontconfig is a nightmare. Without going in details how bad it is, is there a package to replacing it. Or does a earlier version still work?
Markku
Offline
Or does a earlier version still work?
Fortunately I still have version 2.3.2-5, which solves the problem. Before downgrading, remove /var/cache/fontconfig/ and /etc/fonts/
I have uploaded it here if needed:
http://user-contributions.org/projects/pkg/
Markku
Offline
Nightmare in what way? I have 2.4
Why should I downgrade?
Edit: I did it anyway
# rm -r /etc/fonts/ /var/cache/fontconfig/
# pacman -Rd fontconfig
removing fontconfig... /var/lib/pacman/local/fontconfig-2.4.1-4/install: line 61: pushd: /etc/fonts/conf.d: No such file or directory
/var/lib/pacman/local/fontconfig-2.4.1-4/install: line 65: popd: directory stack empty
done.
[root@Nelson martti]# pacman -A fontconfig-2.3.2-5.pkg.tar.gz
loading package data... done.
checking for file conflicts... done.
installing fontconfig... done.
>>>
>>> Bitmap fonts have been disabled by default.
>>> Symlink yes-bitmaps.conf to 10-bitmaps.conf
>>> in /etc/fonts/conf.d to change.
>>>
>>> See /etc/fonts/conf.d/README for more information.
>>>
updating font cache... /usr/bin/fc-cache: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory
done.
I think it is not okay with the expat version I got, or what?
Edit2: X wouldn't come up anymore, cause of old fontconfig, still what's wrong with the new one?
Linux user #438799
Offline
If it works for you, DON'T downgrade!!
The problem what I am getting with 2.4 when fonts are not properly configured, slows down the system (takes long time to load KDE and apps), and fonts are ugly. It can be fixed but too much work.
There are also other threads about the issue, search for "fontconfig".
Markku
Offline
All I can complain about is that some sites use 8pt fonts, those look way too small to read on my screen, so then I force minimum font size to 9. That makes some sites look bad, but I guess that's not the fontconfig issue people are having.
Linux user #438799
Offline
If it works for you, DON'T downgrade!!
The problem what I am getting with 2.4 when fonts are not properly configured, slows down the system (takes long time to load KDE and apps), and fonts are ugly. It can be fixed but too much work.
There are also other threads about the issue, search for "fontconfig".
so have you filed a bug?
Offline
so have you filed a bug?
Done! I was not sure how to describe the bug. I am concluding the problem is in the default settings. Supposed to work out of the box. Or at least after running "fc-cache -f" without the error "failed to write cache" for all installed fonts.
When installing a fresh system from an install CD, I assume the new cache system requires to run "fc-cache" at first boot, after the install. I have noticed its not possible to copy e.g. hd to hd or live cd to hd without the cache error. This cache issue is my "nightmare" when trying to upgrade my Arch Linux Office Install CD. So, I prefer to use the earlier fontconfig.
Markku
Offline
iphitus wrote:so have you filed a bug?
Done! I was not sure how to describe the bug. I am concluding the problem is in the default settings. Supposed to work out of the box. Or at least after running "fc-cache -f" without the error "failed to write cache" for all installed fonts.
When installing a fresh system from an install CD, I assume the new cache system requires to run "fc-cache" at first boot, after the install. I have noticed its not possible to copy e.g. hd to hd or live cd to hd without the cache error. This cache issue is my "nightmare" when trying to upgrade my Arch Linux Office Install CD. So, I prefer to use the earlier fontconfig.
I suppose to start with, the font packages should run fc-cache after being installed. As for copying liveCD -> HD, it's just another step for the installer to deal with, another line in a script.
James
Offline
fontconfig 2.4.2-1 works fine and upgrades smoothly from 2.3.2-5.
Markku
Offline
Take a look in your terminal for warnings with 2.4.2, it should list the reason about why 2.4.1 failed. The cause is a broken /etc/fonts/fonts.conf, which gives you a hint at line 7
Offline
I've just freshly installed Arch 0.8.0 and get a lot of "failed to write cache" error when running fc-cache. How can I solve these errors since I guess this is the reason why my gnome is running very slow now. Most of the apps take around 10s to start (no hdd activities).
Offline
I noticed the same problem.
Markku
Offline
has any solution been found? I really wish this would be solved, I am noticing the same problem.
fc-cache -f gives failed to write cache errors :-(
Offline
Wheee! Got a solution!
It seems that this problem is not that uncommon. I googled for "fontconfig failed to write cache" and found that some folks at ubuntu had also found this problem. I looked at a debian thread discussing the same issue and found that fc-cache cops out if the directories it is trying to setup a cache for have a modification time in the future.
So the quick fix is to simply 'touch' all the directories in /usr/share/fonts/ and run fc-cache -f. Now my apps are back at full speed :-)
Offline
Offtopic, does anyone know how I can create a flyspray account, or else if it can't be done, someone please update the bug in flyspray (http://bugs.archlinux.org/task/6024) This is a really annoying bug.
Offline
Offline