Description of Problem: After upgrade to kdebase-3.0.3-14 (from 3.0.3-13) X server fails on reboot. Error message says: can't find default font "fixed". I have seen this on four or five machines (also with RH 7.3). What these machines have in common is they all have Nvidia graphics cards and they are all using Nvidia drivers. The problem can be worked around in two ways. 1. Revert to 3.0.3-13. or 2. Touch the file /usr/X11R6/lib/X11/fonts/misc/fonts.alias I don't know why 2. works, but it seems to. Version-Release number of selected component (if applicable): How Reproducible: Steps to Reproduce: 1. upgrade to kdebase-3.0.3-14 (from 3.0.3-13) 2. reboot 3. Actual Results: X server fails to start Expected Results: working X Additional Information: Seems related to Nvidia graphics drivers, I don't know how.
it looks like that XFree86-base-fonts was not installed on your machine. It's strange, because it's installed as default! anyway you should install it and it will work again afterwards. Question: as i know i did not release kdebase-3.0.3-14. where have you got this rpm?
I have seen this on four computers running RH 7.3 and RH 8.0. All of them have XFree86-base-fonts-4.2.0-8 from RH installed. As a security policy we install all upgrades from updates.redhat.com. We check redhat signatures before installing. Two days ago there was a massive upgrade of kde (which we mostly do not use but have installed on some machines). This included kdebase-3.0.3-0.7.2.i386.rpm for RH 7.3 and kdebase-3.0.3-14 (Upgraded from 3.0.3-13) on RH 8.0. This upgrade package included two fonts /usr/X11R6/lib/X11/fonts/misc/console8x16.pcf.gz /usr/X11R6/lib/X11/fonts/misc/console8x8.pcf.gz Somehow this broke X. Touching the file /usr/X11R6/lib/X11/fonts/misc/fonts.alias fixes it.
I believe this bug is a duplicate of 79415. It sure would have been nice to hear that from someone who knows more than I do. I wonder if my "fix" of touching the fonts.alias file and rebooting causes the fonts.dir file to be rewritten with correct permissions, thus solving the problem (see 79415).
*** Bug 84609 has been marked as a duplicate of this bug. ***