Bug 22926 - problems with xfs _FontTrans
problems with xfs _FontTrans
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2000-12-27 22:59 EST by daz7997
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-01 16:27:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description daz7997 2000-12-27 22:59:58 EST
xfs seems to start correctly during init sequence, but by the time the
machine gets to the end of booting to runlevel 5, xfs is dead, with a lock
file still hanging around.  In the boot log, there is an error:

_FontTransSocketINETCreateListener: Unable to get service for -1
_FontTransMakeAllCOTSServerListeners: failed to create listener for tcp

and messages that xfs has shutdown successfully after that.  Does xfs try
to get something via TCP, can't find it, then kills itself and leaves it's
carcass in /var/lock/subsys?

Comment 1 Bill Nottingham 2000-12-28 11:02:43 EST
Is this using the X that shipped with 6.2, or did you install different

The XFree86 packages that shipped with 6.2 have important patches
for the font server that may not exist in other packagings...
Comment 2 daz7997 2000-12-28 15:12:18 EST
This is X that came with 6.2 yes.  It was running fine for a while, then I tried
to install some new fonts, accidentally deleted the old ones, then I removed all
the fonts, and re-installed them all again from the 6.2 install CD.

Was there a special file in the fonts directories that xfs needs?  Can I
recreate it?  Is this a dead end?
Comment 3 Mike A. Harris 2001-03-17 14:23:23 EST
Use mkfontdir in the font directories to recreate any fonts.dir files.

Note You need to log in before you can comment on or make changes to this bug.