Bug 1269 – startx dies with font error until xfs is restarted

Bug 1269 - startx dies with font error until xfs is restarted

Summary:	startx dies with font error until xfs is restarted

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	XFree86 (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Cristian Gafton
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-02-21 14:45 EST by Chris Runge
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-03-18 19:33:22 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Chris Runge 1999-02-21 14:45:29 EST

RHL 5.8.1 (Beta 1)

Upgraded 5.8 to 5.8.1, created a normal user, logged in as
that user, and typed startx.  This error appeared:


_FontTransSocketINETConnect: Can't connect: errno = 111
failed to set default font path 'tcp/localhost:7100'
Fatal server error:
could not open default font 'fixed'

When reporting a problem related to a server crash, please
send the full server output, not just the last messages

X connection to :0.0 broken (explicit kill or server
shutdown).


as root I did this:
/etc/rc.d/init.d/xfs restart


I can then do a startx again and it works fine.

NOTE: this happened immediately after the upgrade and after
a reboot (perhaps xfs is not initializing properly upon
boot?)

Comment 1 Cristian Gafton 1999-03-18 19:33:59 EST

xfs was not starting by default on boot. Should be fixed now in the
beta release.

Comment 2 Matthew Miller 2000-04-18 20:37:59 EDT

I'm still seeing this occasionally on 6.2 final systems. (Fresh installs.) I
can't figure it out or make it reproducable, unfortunately, but this IS still a
problem. :(

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