Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: mark AT nospam DOT emardi DOT demon DOT co DOT uk To: cygwin AT cygwin DOT com Reply-to: mark AT emardi DOT demon DOT co DOT uk Subject: cygwin 1.13.11-3 and Xwindows Date: Mon, 01 Jul 2002 13:54:06 +0100 User-Agent: Demon-WebMail/2.0 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: Hi, I've just upgraded by cygwin installation to DLL 1.13.11-3. I'm now not able to start X-Windows - I get the following after doing a startx: waiting for X server to shut down XIO: fatal IO error 110 (Cannot send after tr ansport endpoint shutdown) on X server ":0.0" after 198 requests (196 known processed) with 3 events remaining. XIO: fatal IO error 110 (Cannot send after transport endpoint shutdown) on X se rver ":0.0" after 44 requests (42 known processed) with 0 events remaining. Cygwin is running on NT workstation - SP6a. The X server seems to be dying when xterm tried to start. Starting up the server and twm by hand, everything is fine. However, if I start an "xterm -hold", the xterm reports "setuid failed: Invalid arguement". Looking at the release notes, I see that there have been changes to the uid and gid code. Anything to do with it? Thanks Mark Doutre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/