Red Hat Bugzilla – Bug 59032
Fatal server error: could not open default font 'fixed'
Last modified: 2005-10-31 17:00:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; SunOS 5.8 sun4u)
Description of problem:
I did a fresh install of RH7.2 in November, and have routinely
run the Red Hat update agent each week to keep the system current.
On Sunday I ran the update agent, which included both kernel update
and XFree86 updates, among others. The next time I rebooted,
X11 didn't work at all. I could run Xconfigurator and see the test
screen, but couldn't launch X.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.change permissions on fonts.dir to 600
2. restart xfs
3. run 'startx' or reboot
I saw a similar report on comp.os.linux.x, which pointed to the
problem. It turns out that /usr/X11R6/lib/X11/fonts/misc/fonts.dir
was not world-readable. Its permissions were -rw-------, and
it was owned by root. I changed this file to be world-readable,
which didn't immediately fix the problem, until I realized I needed
to restart xfs (/sbin/xfs -restart). This completely restored X11.
I consider this to be an extremely serious bug because , although
trivial to fix, it completely kill X11, which means you don't
even have access to a browser, newsgroups, multiple windows,
admin tools -- al l the things that make it possible to discover
the problem. It essentially makes the whole system uselessl.
I think Red Hat should send an email announcement about this
bug to all up2date users, in addition to fixing the release of XFree86
that is downloaded by up2date.
(Note: I will attach log files for XFree86 and up2date with this report).
Created attachment 43937 [details]
Tar archive with log files for XFree86.0 and up2date
This problem can be caused by a great many things. It is highly dependant
on how one has configured their system, and various other factors, and is
not due to a single pinpointable cause. In order to conclude it is a bug
in the released packages, you'd have to troubleshoot it to determine the
exact cause of the problem and report that. More likely than not, it is a
local issue, and not a bug in the packaging - otherwise you wouldn't be
the only person to have reported this.