Fatal X Server Error

2004-06-06 Thread Barry Skidmore
I believe I am having a problem with the xserver failing whenever my monitor's DPMS kicks in. After either windowmaker or enlightenment have run for 15 minutes, the window manager quits and I am put back into the console with the following errors: Fatal server error: Caught signal 4. Server

Re: fatal X server error

2001-10-24 Thread j
On Wednesday 24 October 2001 09:28, Rikki Hall wrote: > Others have had this problem and solved it by reinstalling xfonts > packages, i removed all fonts and then installed them again. it worked. kinda. It failed again when i added xfonts-scalable btw: what is defoma and can it help in this

fatal X server error

2001-10-24 Thread Rikki Hall
X is failing thusly: Fatal server error: could not open default font 'fixed' Others have had this problem and solved it by reinstalling xfonts packages, but I have done a forced reinstall ('apt-get --reinstall install ...') of xfonts-base, xfonts-100dpi, xfonts-75dpi, and xfonts-scalable, and it

Re: Fatal X server error.

2001-07-27 Thread Christopher S. Swingley
Chip, > I am having a problem with startx. The error message says: > Fatal server error: > could not open default font 'fixed' Do you have the font packages installed, like xfonts-base, xfonts-75dpi, xfonts-100dpi, xfonts-scalable? You don't say what version of X you are running, but the versio

Re: Fatal X server error.

2001-07-27 Thread Alvin Oga
hi ya fu you need to hav xfs running... or comment out "unix/:-1" from your /etc/X11/XF86Ccnfig file and add some explicitly defined FontPaths ... # make sure you have the directories you list FontPath"/usr/X11R6/lib/X11/fonts/100dpi" ... c ya alvin = = http

Fatal X server error.

2001-07-27 Thread Fu-Dong Chiou
Hi, I am having a problem with startx. The error message says: _FontTransSocketUNIXConnect: Can't connect: errno = 2 failed to set default font path 'unix/:-1' Fatal server error: could not open default font 'fixed' XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0

Re: new X server error

2000-10-12 Thread Max Kamenetsky
* Michiel Meeuwissen <[EMAIL PROTECTED]> [10/12/00 12:46] wrote: > Max Kamenetsky <[EMAIL PROTECTED]> skribis: > > After upgrading to the latest and greatest version of woody today, I > > am getting the following error whenever I try to start X: > > > > > > Fatal server error: > > could not open

Re: new X server error

2000-10-11 Thread kmself
On Wed, Oct 11, 2000 at 04:13:39PM -0700, Max Kamenetsky ([EMAIL PROTECTED]) wrote: > After upgrading to the latest and greatest version of woody today, I > am getting the following error whenever I try to start X: > > > Fatal server error: > could not open default font 'fixed' Are you running

new X server error

2000-10-11 Thread Max Kamenetsky
After upgrading to the latest and greatest version of woody today, I am getting the following error whenever I try to start X: Fatal server error: could not open default font 'fixed' Does anyone know how to fix this? Thanks a lot for any help and please cc me on your responses. Max

Re: X server error

2000-06-23 Thread Corey Popelier
Yeah I also fixed this by deleting all . directories under /tmp. Cheers, Corey Popelier http://members.dingoblue.net.au/~pancreas Work Email: [EMAIL PROTECTED] On Fri, 23 Jun 2000, ARTUS Guillaume wrote: > Max Kamenetsky wrote: > > > > I just upgraded to the latest version of X in unstable a

Re: X server error

2000-06-23 Thread ARTUS Guillaume
Max Kamenetsky wrote: > > I just upgraded to the latest version of X in unstable and here's the > error I get when trying to run startx: > > X: server socket directory has suspicious ownership, aborting > _X11TransSocketUNIXConnect: Can't connect: errno = 111 > giving up. > > xinit then bombs ou

Re: X server error

2000-06-22 Thread Mike Werner
Max Kamenetsky wrote: > I just upgraded to the latest version of X in unstable and here's the > error I get when trying to run startx: > > X: server socket directory has suspicious ownership, aborting > _X11TransSocketUNIXConnect: Can't connect: errno = 111 > giving up. > > xinit then bombs out a

X server error

2000-06-22 Thread Max Kamenetsky
I just upgraded to the latest version of X in unstable and here's the error I get when trying to run startx: X: server socket directory has suspicious ownership, aborting _X11TransSocketUNIXConnect: Can't connect: errno = 111 giving up. xinit then bombs out and tells me that it cannot connect to

Re: Fatal X server error

2000-04-13 Thread Charles Lewis
After saving the settings and exiting, it kicks us back to the prompt, so I was assuming the server was indeed dead. Charles Lewis [EMAIL PROTECTED] > > However, after saving > > the settings and type startx we get the following error: > > > > -

Re: Fatal X server error

2000-04-13 Thread Oswald Buddenhagen
> However, after saving > the settings and type startx we get the following error: > > -- > _XSERVTransSocketINETCreateListener: ...SocketCreateList > ener() failed > _XSERVTransMakeAllCOTSServerListeners: server already > running > did you shut d

Fatal X server error

2000-04-13 Thread lewisc
Trying to install X (3.3.6) Have tried 3 different video cars (S3 Trio64/DX, S3d Virge DX, Matrox Millenium PCI), so I\'m pretty sure the problem is our ignorance. With the Matrox e were able to use XF86Setup to start up, did a vidtune, etc. However, after saving the settings and type startx w

X server error output (Re: X11 problems)

1996-08-05 Thread Ed Donovan
[EMAIL PROTECTED] (Jens Decker) writes: > > The monitor gets black and after CTRL-ALT-F4 I get: > > TRANS(SocketUNIXConnect) () can't connect: errno = 111 > giving up. > xinit: Connection refused (errno 111): unable to connect to X server > xinit: No such process (errno 3): Server error. >