Message-Id:	<201505151926.t4FJQdFx027779@delorie.com>
X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date; q=dns; s=default; b=jeMx
	cGD0X0SXn1ickDIMmMPD8ijRXvMMS7TZs+3z2Poeg63yvPXqMDKq7+PULTK8iRRC
	iPy+oUQXH80a3DTS+15DvkWoyC8tCdYzQTzmHUqVLIcQO6QGeDP4AENcDWuezNd4
	g8lMcgVCZu5GwF9jqmE+wr4KW4iqIx73JYll770=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date; s=default; bh=0Nc4CluYja
	LLiHhHZZ6KrM9yLZA=; b=lSDsRJM+ayPJZOI3XohABGZy3OpPU/1z7RPtO56vzO
	UYyReVAJZaSKXfIcWoibyIP3vXcV5jipL9NikZtXDJvempdmgHq8LA57LRPaU6bk
	r82xbwLtZsCNibFeiGl5ldE5e8V8qRFnPeCV9lUJ8ey4EABkiZkHYjEfuZvqStVc
	c=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=3.5 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,MISSING_MID,RDNS_DYNAMIC,TVD_RCVD_IP autolearn=no version=3.3.2
X-HELO:	genesis.homeaccesshealth.com
From:	bgoldberg AT homeaccess DOT com
To:	cygwin AT cygwin DOT com
Subject:	startxwin - unable connect X server - ver 1.16.2 fails; invalid window param???
Date:	Fri, 15 May 2015 19:03:51 +0000
X-IsSubscribed:	yes

Running cygwin32 under xp; recently updated to 1.17; And Xwin server is now broken.

As referenced in Chris Kunz' post (and my reply to):
Xwin does a core dump and won't start.

Having not seen any workarounds - I tried reverting my xorg packages back to 1.16.2 which was last known working for me.

STILL BROKEN!
Although - at least xwin is not core dumping - and I AM getting info in the log (below).

Does anyone have any more wisdom or ideas they can add?
TIA - Bob

/var/log/xwin/xwin.0.log:
---
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.16.2.0
OS: CYGWIN_NT-5.1 windozer 1.7.33-2(0.280/5/3) 2014-11-13 15:45 i686
OS: Windows XP Service Pack 3 [Windows NT 5.1 build 2600] (Win32)
Package: version 1.16.2-1 built 2014-11-11

XWin was started with the following command line:

X :0 -multiwindow

ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1440 h 900 winInitializeScreenDefaults - native DPI x 96 y 96
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/proteus:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
(II) xorg.conf is not supported
[   604.109] (II) xorg.conf is not supported

(( ..SNIP..))

winInitMultiWindowWM - DISPLAY=:0.0
[   630.750] winInitMultiWindowWM - DISPLAY=:0.0
winMultiWindowXMsgProc - DISPLAY=:0.0
[   630.750] winMultiWindowXMsgProc - DISPLAY=:0.0
winProcEstablishConnection - winInitClipboard returned.
[   630.812] winProcEstablishConnection - winInitClipboard returned.
winClipboardThreadProc - DISPLAY=:0.0
[   630.812] winClipboardThreadProc - DISPLAY=:0.0
OS maintains clipboard viewer chain: no
[   630.812] OS maintains clipboard viewer chain: no
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp lay.
[   630.875] winInitMultiWindowWM - XOpenDisplay () returned and successfully op
ened the display.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di splay.
[   630.875] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully
opened the display.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
[   630.875] winClipboardProc - XOpenDisplay () returned and successfully opened
 the display.
executing 'xterm', pid 5712
[   667.984] executing 'xterm', pid 5712
(pid 5712 stderr) Warning: Missing charsets in String to FontSet conversion
[   668.218] (pid 5712 stderr) Warning: Missing charsets in String to FontSet co
nversion
executing 'xterm', pid 4740
[  9148.765] executing 'xterm', pid 4740 (pid 4740 stderr) Warning: Missing charsets in String to FontSet conversion [  9149.125] (pid 4740 stderr) Warning: Missing charsets in String to FontSet co nversion winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attribut
es)
[ 11376.218] winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid param eter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) [ 11424.812] winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Wind ow parameter) winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) [ 11424.812] winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Wind ow parameter) winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) [ 11424.812] winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Wind ow parameter) OS has icon alpha channel support: yes [ 11425.515] OS has icon alpha channel support: yes winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter)
---

end of log



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -