Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Thu, 27 Jun 2002 11:10:16 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-xfree AT cygwin DOT com, cygwin AT cygwin DOT com
Subject: Re: Progress? Still debugging [cgf or someone from cygwin list please comment]
Message-ID: <20020627151016.GE5126@redhat.com>
Reply-To: cygwin-xfree AT cygwin DOT com, cygwin AT cygwin DOT com
Mail-Followup-To: cygwin-xfree AT cygwin DOT com, cygwin AT cygwin DOT com
References: <200206271450 DOT g5REoTd85420 AT pilot20 DOT cl DOT msu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200206271450.g5REoTd85420@pilot20.cl.msu.edu>
User-Agent: Mutt/1.3.23.1i

On Thu, Jun 27, 2002 at 10:50:28AM -0400, Harold L Hunt wrote:
>[Please be careful to only reply to cygwin-xfree AT cygwin DOT com, I am only sending
>this to cygwin AT cygwin DOT com so that the Cygwin folks know what is going on.]
>
>Non-xterm clients work fine.  xterm does not work.
>
>The base problem here is that xterm calls getuid () to find out what the
>current process's user id is.  Then it later calls setuid (), passing the same
>value that was returned by getuid ().  For some reason, regardless of whether
>you have run 'mkpasswd -d -u user_name >> /etc/passwd', the call to setuid ()
>fails with Permission Denied.
>
>This is not something that the Cygwin/XFree86 folks changed, rather it was
>something that was changed in Cygwin proper (think cygwin1.dll).  From our
>perspective, and probably from the perspective of the Cygwin developers,
>cygwin1.dll is broken when Cygwin/XFree86 doesn't work right.
>
>Thus, I'm going to guess that the Cygwin folks are working on this and that
>you need to start testing the latest cygwin1.dll snapshots to help them, and
>us, figure out when the problem is fixed.  I've got a machine now that has the
>same problem so I will be testing snapshots as well, once a compile job finishes.
>
>Here is some information on installing a snapshot release of cygwin1.dll:
>http://cygwin.com/ml/cygwin-xfree/2002-06/msg00383.html

Thanks for *trying* a snapshot, Harold, and reporting on your experiences.

I guess we'll keep plugging at this.  My time is very limited but I'll
try to debug this X problem as soon as I have a chance.

Until then if someone could 1) Try the very latest snapshot (the
2002-06-26 snapshot changed several times yesterday) and 2) post an
strace from a failing xterm.  It would help enormously.

cgf

--
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/