Comments on: Cygwin/X XWin Server leaves an xterm window behind when starting

By: Oly

Oly — Sun, 28 Nov 2010 23:18:51 +0000

I’m using 1.9.2 … now I have managed to get the server start failure even without .startxwinrc (though not as often – happens every time if I have a .startxwinrc). There are similar reports dating back a year ago (“another window manager is running”) but no solutions to be found. So, I’m stuck … but it isn’t purely about the .startxwinrc.

By: Aaron

Aaron — Sun, 28 Nov 2010 18:04:02 +0000

I updated to the current version of the Xwin server today (1.9.2 built on 2010-11-03) and everything seems to be working as expected.

By: Oly

Oly — Thu, 25 Nov 2010 16:55:08 +0000

Been using this for a while … but a couple of days ago, it started preventing the server from starting. Now, if I have the empty .startxwinrc file there the server complains:

[ 22137.468] winMultiWindowXMsgProc – another window manager is running. Exiting.
[ 22137.468] winClipboardProc – winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop.
[ 22137.468] winClipboardProc – XDestroyWindow succeeded.
[ 22137.468] winClipboardProc – Clipboard disabled – Exit from server
[ 22137.468] winMultiWindowXMsgProcIOErrorHandler!

By: Zach

Zach — Mon, 20 Sep 2010 19:02:05 +0000

That’s really handy, thanks!

By: Steven

Steven — Thu, 17 Jun 2010 16:12:31 +0000

Thanks for posting this! What a simple solution to an otherwise annoying little problem!