Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Jul 1998 19:25:34 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc:        alk@pobox.com, current@FreeBSD.ORG
Subject:   Re: State of current...
Message-ID:  <19980717192534.B342@freebie.lemis.com>
In-Reply-To: <6601.900665763@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Jul 17, 1998 at 10:56:03AM %2B0200
References:  <19980717173714.Q566@freebie.lemis.com> <6601.900665763@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 17 July 1998 at 10:56:03 +0200, Poul-Henning Kamp wrote:
>> On Friday, 17 July 1998 at  1:01:45 -0500, Tony Kimball wrote:
>>> FYI:  After good function and stability at the beginning of the month,
>>> it's starting to look pretty sad...  rcmds to foreign platforms are
>>> not working (again--resurrecting an *old* bug),  X applications are
>>> failing (in particular:
>>> netscape: X Error of failed request:  BadPixmap (invalid Pixmap parameter)
>>>   Major opcode of failed request:  56 (X_ChangeGC)
>>>   Resource id in failed request:  0x50038
>>>   Serial number of failed request:  117146
>>>   Current serial number in output stream:  117380
>>>
>>> netscape: X Error of failed request:  BadLength (poly request too large or internal Xlib length error)
>>>   Major opcode of failed request:  22 (X_SetSelectionOwner)
>>>   Serial number of failed request:  117147
>>>   Current serial number in output stream:  117380
>>> etc.) And yesterday xemacs wrote a bunch of nulls instead of the
>>> proper end of the source file I was editing (realloc failing to copy perhaps?).
>>> In all, pretty shaky.
>>
>> I was wondering if something was wrong, too.  I haven't had this
>> particular problem, but I've had a number of processes, including
>> Emacs, hang in select after VisibilityNotify events, unable to update
>> their displays.  It's nothing enough to be sure that anything's wrong,
>> but enough to be noticable.  I'm rebuilding with the latest -current
>> (as of about 2 hours ago), and will try again.
>
> I've seen this problem too.

It still seems to be there with the latest -current.

Greg
--
See complete headers for address and phone numbers
finger grog@lemis.com for PGP public key

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980717192534.B342>