Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!bionet!agate!ucbvax!decwrl!sun!snafu!lm
From: lm@snafu.Sun.COM (Larry McVoy)
Newsgroups: comp.windows.x
Subject: Re: Is there a mail address for X bugs?
Message-ID: <97827@sun.Eng.Sun.COM>
Date: 6 Apr 89 18:42:56 GMT
References: <97367@sun.Eng.Sun.COM> <8904041045.AA11260@EXPIRE.LCS.MIT.EDU>
Sender: news@sun.Eng.Sun.COM
Reply-To: lm@sun.UUCP (Larry McVoy)
Organization: Sun Microsystems, Mountain View
Lines: 25

I wrote:

Where do I send X bugs?

And Bob wrote:
>(If you drag around at MIT X tape, then you should have by now read the
>release notes, which tell you where to send bugs.)  Send bug reports to
>xbugs@expo.lcs.mit.edu, using the form in doc/bugs/bug-report.
>MIT will fix bugs based on their relative priority to other tasks/bugs that
>we need to get done/fixed.  I can't be more specific than that.  If you are
>working with Sun on SunOS 4.1, then presumably you can work through your
>channels to deal with Sun on their product release of X.

Silly me, I suppose I should read the release notes (still haven't and
X runs file :-)  Anyway, I just wanted people to know that X was not
the problem - the problem was that fcntl(fd, F_SETOWN, getpid()) was
implemented as ioctl(fd, TIOCSPGRP, &mypid) and as such fell victim to
stricter POSIX checking than it used to.  In particular, POSIX refused
to believe that the mouse and kbd were controlling tty's (can't imagine
why :-) The bug has been fixed, X is redeemed, and all is wonderful.

Thanks to all who commented on this,


Larry McVoy, Lachman Associates.			...!sun!lm or lm@sun.com