From owner-freebsd-current Fri Jul 17 01:59:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08581 for freebsd-current-outgoing; Fri, 17 Jul 1998 01:59:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08566 for ; Fri, 17 Jul 1998 01:59:25 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id KAA06603; Fri, 17 Jul 1998 10:56:03 +0200 (CEST) To: Greg Lehey cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: State of current... In-reply-to: Your message of "Fri, 17 Jul 1998 17:37:14 +0930." <19980717173714.Q566@freebie.lemis.com> Date: Fri, 17 Jul 1998 10:56:03 +0200 Message-ID: <6601.900665763@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen this problem too. In message <19980717173714.Q566@freebie.lemis.com>, Greg Lehey writes: >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. > >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 > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message