r j wrote:
The new config file for 4.0.2 is XF86Config. Unfortunately, and don't
ask why cause i don't know yet, X is using the XF86Config-4 file when
it starts. Apparently the font path unix/:-1 is no longer
acceptable.???smh???
Create a new XF86Config with xf86config from the console,
Ahhh. Thanks. :-)
Merry Christmas!
rj
==
--- Antony Suter [EMAIL PROTECTED] wrote:
r j wrote:
The new config file for 4.0.2 is XF86Config. Unfortunately, and
don't
ask why cause i don't know yet, X is using the
On a stock 7.2 box upgraded to cooker recently:
XFree86 4.0.2 reports
_FontTransSocketUNIXConnect: Can't connect: errno = 2
failed to set default font path 'unix/:-1'
Fatal server error:
could not open default font 'fixed'
i have *4.0.2-1mdk* installed, and have tried with multiple video
On Friday 22 December 2000 13:46, you wrote:
On a stock 7.2 box upgraded to cooker recently:
XFree86 4.0.2 reports
_FontTransSocketUNIXConnect: Can't connect: errno = 2
failed to set default font path 'unix/:-1'
Fatal server error:
could not open default font 'fixed'
i have *4.0.2-1mdk*
It sounds as if your font server hasn't been started.
-Original Message-
From: Shalrath [mailto:[EMAIL PROTECTED]]
Sent: 22 December 2000 12:47
To: Cooker
Subject: [Cooker] problem with XFree 4.0.2
On a stock 7.2 box upgraded to cooker recently:
XFree86 4.0.2 reports
Check to see if the font server is running. As root do this:
cd /etc/init.d
ls (see if xfs is there)
./xfs start
Axel - 584
On a stock 7.2 box upgraded to cooker recently:
XFree86 4.0.2 reports
_FontTransSocketUNIXConnect: Can't connect: errno = 2
failed to set default font path
On Friday 22 December 2000 06:58, Axel R. wrote:
Check to see if the font server is running. As root do this:
cd /etc/init.d
ls (see if xfs is there)
./xfs start
A cleaner way:
# rpm -q XFree86-xfsthis must be installed!
# chkconfig --list xfs
If it's not started at run
civileme [EMAIL PROTECTED] writes:
On Friday 22 December 2000 13:46, you wrote:
On a stock 7.2 box upgraded to cooker recently:
XFree86 4.0.2 reports
_FontTransSocketUNIXConnect: Can't connect: errno = 2
failed to set default font path 'unix/:-1'
Fatal server error:
could not open
I agree with Steve:
your font server is not running.
I found that sometimes it happens when you are limited on disk space.
Check that you have at least 150MB on your HDD, and reboot computer.
I was getting such message with 60MB of free disk space.
Annoying, isn't it?
Friday 22 December 2000
I am aware of xfs
The problem persists however. xfs is running before and after trying to
startx.
[root@helios /root]# xfs
FontCacheInitialize: hi=1048576, lo=786432, bal=70
Is something causing xfs to malfunction?
Jason
On Fri, 22 Dec 2000, Shalrath wrote:
I am aware of xfs
The problem persists however. xfs is running before and after trying to
startx.
[root@helios /root]# xfs
FontCacheInitialize: hi=1048576, lo=786432, bal=70
Is something causing xfs to malfunction?
How X is trying to
11 matches
Mail list logo
