From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060126 Fedora/1.5-5 Firefox/1.5
Description of problem:
unable to boot into gui after yesterdays update
Attached bad ~/.font.cache-2 file
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.login as root or user
Actual Results: Hangs at KDE or GNOME splash screen
Expected Results: Boot gui
Work around delete ~/.font.cache-2 file for each user
according to bill nottingham:
Created attachment 124072 [details]
corrupt .fonts.cache-2 file
Some of us also found that not having a .fonts directory with a fonts.dir
inside lead to a crash during the early login.
I got this after updating to FC 5.
I found that a new user could log in find, but my existing one couldn't.
I played around with removing various dotfiles from my home directory until I
found out which one was the problem - it was the .fonts.cache-2 files.
This is a serious bug - as I say, after upgrading to FC5, I couldn't log in any
The severity of this bug should be upgraded to "high" or "urgent". Not being
able to log in after upgrading is not a "Normal" priority bug.
close this bug ...
Dex: Why? Has it been fixed? I worked round it by removing files - but will it
occur again on future upgrades?
This was caused by early versions of fontconfig 2.3.x that were in some test
releases of fedora. The actual bug has been long fixed.
Comment on #7: I've never run a test release; this bug was in the gold master
of FC5 which I was running. I'm glad to hear that it's apparently fixed now,
though the comment that it was in a test makes me wonder if it's the same bug?