From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686)
Description of problem:
Using xfontsel, we can repeatedly lock the Xserver. The machine becomes
completely unusable from the main console. You cannot switch to a text
console or kill the X server with ctrl-backspace. You can still log in
remotely but root cannot kill any X related processes. Init 3 has no
effect either. The only recourse is a reboot. We can do this on any
Redhat 7.1 (SGI XFS 1.01) machine we have. It does not matter what video
card or driver we are running.
Version-Release number of selected component (if applicable):
rpm -qf /usr/X11R6/bin/xfontsel
Steps to Reproduce:
2.pick misc(fndry) fixed(fmly) ptsz(160)
3.machine locks hard. Power cycle or reboot from a remote connection.
Actual Results: The machine locks the graphics display hard.
Expected Results: I should be able to pick a font. Some combinations
work. The above one always
results in a lockup.
I have seen similar display lockups as well but never reproducible like
I've reproduced this on a 16Mb Voodoo 3 AGP card as root and user,
in 1024x768x16 with DRI enabled.
On a Radeon QD (5144) however it does not crash. It does act odd
however, and display an improper font table. Switching to 140/200/etc.
works, choosing 160 displays only "N/L".
There is definitely a bug here. Can you please provide me a list of
some hardware you've tried this on and could reproduce, and also
add your X configuration and X log files as file attachments using
the link below?
It might aide me in debugging. Thanks for your bug report.
This problem appears to be fixed in current rawhide XFree86. It may or may
not be fixed in XFree86 4.2.0 or 4.2.1 perhaps also. I don't have a 4.2.x
setup currently installed to test with however.
Have you tried RHL 7.2/7.3 or 8.0? Just curious if anyone is able to
reproduce the problem on any of those releases?
Ok, I've just got a whackload of guinea pigs in IRC to test this in 7.3 and 8.0
on a wild array of hardware. So far no lockups reported. I'm going to close
this one as fixed in Red Hat Linux 7.3 and 8.0 for now, but if you find the
problem still exists in any release please reopen.