X fails

[Richard R. Sivernell]

On Tue, 02 Jul 2002 19:42:34 -0700
"Net Llama!" <netllama at linux-sxs.org> wrote:

> rick, i think we need a bit more info to go on here.  it seems that X 
> isn't configured for remote display, perhaps?  or you're blocking port 6000?
> 
Lonnie

   eServer 3.1.1  xfree 4.2 stock install. kernel 2.4.13,I think,
if I try to start gui with kdm  a black screen for a while, then it returns
to run level 3. If I try then, after login, startkde startxfce, startx

[root at Sivernell root]# startx
XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 January 2002
        If the server is older than 6-12 months, or if your card is
        newer than the above date, look for a newer version before
        reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.9-13smp i686 [ELF]
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Jul  3 08:13:38 2002
(==) Using config file: "/etc/X11/XF86Config-4"


Fatal server error:

_LoaderFileToMem() read() failed: Input/output error


When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to xfree86 at xfree86.org.

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.
[root at Sivernell root]#


[root at Sivernell root]# startxfce
/usr/bin/startxfce: X server already running on display :0.0
xsetroot:  unable to open display ':0.0'
xset:  unable to open display ":0.0"
xfwm message (type main): Error = can't open display :0.0
[root at Sivernell root]# xscreensaver: Can't open display: :0.0
xscreensaver: initial effective uid/gid was root/root (0/0)
xscreensaver: running as nobody/nobody (65534/65534)

xscreensaver: This is probably because you're logging in as root.  You
              shouldn't log in as root: you should log in as a normal user,
              and then `su' as needed.  If you insist on logging in as
              root, you will have to turn off X's security features before
              xscreensaver will work.

              Please read the manual and FAQ for more information:

              http://www.jwz.org/xscreensaver/faq.html
              http://www.jwz.org/xscreensaver/man.html


[root at Sivernell root]#

[root at Sivernell root]# startkde
xsetroot:  unable to open display ':0.0'
xset:  unable to open display ":0.0"
xset:  unable to open display ":0.0"
xset:  unable to open display ":0.0"
ksplash: cannot connect to X server :0.0
DCOPServer up and running.
kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-1788' to 'kded'
ERROR: KUniqueApplication: DCOP communication error!
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kcminit: cannot connect to X server :0.0
knotify: cannot connect to X server :0.0
ERROR: KUniqueApplication: Registering failed!
ERROR: KUniqueApplication: DCOP communication error!
ksmserver: cannot connect to X server :0.0
[root at Sivernell root]# hotpluguid: cannot connect to X server :0.0
ERROR: KUniqueApplication: Registering failed!
ERROR: KUniqueApplication: DCOP communication error!

[root at Sivernell root]#


If I login thru ssh or run at the actual machine the result is the same.

How would I check to see if port 6000 is being blocked 

Thanks  cheers
-- 
Rick Sivernell
Dallas, Texas  75287
972 306-2296
res005ru at gte.net
Caldera Open Linux eWorkStation 3.1.1
Registered Linux User

   .~.
  / v \
 /( _ )\
   ^ ^
In Linux we trust!