Ismet, Thanks for working on this. I removed /tmp/ksocket-kdtop and /tmp/ksocket-root and rebooted. ->no difference.
It still wants to take my vncserver session into the gnome desktop. It seems like before I might have run vncserver from the console, after logging in with a kde desktop. Maybe I'll try that.... Thanks again Kevin On 11/9/05, Ismet Kursunoglu <[EMAIL PROTECTED]> wrote: > > I found a log file that has lots of lines that look like this: > > ---------------------------------------------- > > Window manager warning: Adding client to server's list failed, CORBA > > error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 > > Window manager warning: Adding client to server's list failed, CORBA > > error: IDL:omg.org/CORBA/COMM_FAILURE:1.0 > > Looks like some references to lock files or old socket tmp files or gnome conf > files? > I don't know if RH server clears /tmp on reboots, but you might try removing > any references > to X files, sockets or gnome and then start up X again. > > The startup script for tightvnc sure is more than I am use to but I would > imagine that somehow it is locked? > > My experience is that most common journal file systems are quite reliable > under > Linux (ext3, XFS, reiser) > > -- ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
