On Wednesday 23 January 2002 03:54 pm, Rachel Andrew wrote: > > If you try to start it from the command line, does it produce any errors? > > If so, can you post them here? > > The latest set of errors are below, I've been getting the cannot connect to > X server error intermittently since I did an update about 2 weeks ago that > pulled in some xserver stuff. However everything else seems to run fine (it > will just not let me run XEmacs for example from the commandline as my user > even when su'd to root, if I start KDE with startx after logging in as my > user I don't get these errors, only if I start it from kdm) however KNode > doesn't work as any user.
Well, from the below it looks like you're getting hit with an authorization error. I usually run xhost +localhost in my .xsession file (through I've been told that's horridly insecure, ect) and errors similar to those below don't seem to occur. But I can't claim to have experienced your particular problem with KNode before, so I don't know if that'll help in any way. (Of course I haven't updated my Woody system in four months, so maybe that's why I'm not getting this yet.) <snip> > Xlib: connection to ":0.0" refused by server > Xlib: Client is not authorized to connect to Server > kded: cannot connect to X server :0.0 > DCOP aborting call from 'anonymous-12733' to 'kded' > ERROR: KUniqueApplication: DCOP communication error! > Xlib: connection to ":0.0" refused by server > Xlib: Client is not authorized to connect to Server > kdeinit: Can't connect to the X Server. > kdeinit: Might not terminate at end of session. > Xlib: connection to ":0.0" refused by server > Xlib: Client is not authorized to connect to Server > knode: cannot connect to X server :0.0 <snip>
