I am getting the following error from kdeinit 3.4.1 Xclient running on Cywin(see below at end of listing)when it tries to communicate with the Cygwin/X server: winPointerWarpCursor - Discarding first warp: 400 300 winInitMultiWindowWM - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winProcEstablishConnection - Clipboard is not enabled, returning. access control disabled, clients can connect from any host / winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. kdeinit: Launched DCOPServer, pid = 1028 result = 0 DCOP: register 'anonymous-1028' -> number of clients is now 1 DCOP: unregister 'anonymous-1028' kdeinit: Launched KLauncher, pid = 224 result = 0 DCOP: register 'klauncher' -> number of clients is now 1 DCOP: new daemon klauncher kdeinit: Launched KDED, pid = 3436 result = 0 DCOP: register 'kded' -> number of clients is now 1 DCOP: unregister 'kded' DCOP: register 'kded' -> number of clients is now 1 DCOP: register 'anonymous-3436' -> number of clients is now 2 kio (KDirWatch): Available methods: Stat kdeinit: Got EXT_EXEC 'kbuildsycoca' from launcher. Unknown ClientMessage Unknown ClientMessage Unknown ClientMessage Unknown ClientMessage Unknown ClientMessage kio (KLauncher): kbuildsycoca (pid 1076) up and running. winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) Unknown ClientMessage Unknown ClientMessage As can be seen in the listing above the Cygwin Xserver is opening correctly. The Xserver is visable in the windows XP system tray, but there are no KDE windows visable in the Xserver only the grey root display. How do I configure my choice of window manager with KDE on Cygwin and could that be the problem here?
Is there a method to get more detailed diagnosic messages from the Cygwin Xserver? /Ross