Date: Fri, 17 Jul 1998 16:13:50 +0200 (CEST) From: Henry Vogt <henry@MX.BA-Stuttgart.De> To: grog@lemis.com (Greg Lehey) Cc: phk@critter.freebsd.dk, alk@pobox.com, current@FreeBSD.ORG Subject: Re: State of current... Message-ID: <199807171413.QAA02990@marylin.goethestr12-net.marbach-neckar> In-Reply-To: <19980717192534.B342@freebie.lemis.com> from Greg Lehey at "Jul 17, 98 07:25:34 pm"
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 > -- Yes, i'm running SMP 3.0-Current here and there are at least two more essential programs (xdvi and gv) with this very problems.. Someone on the list mentioned a few days ago using DISPLAY=localhost:0.0, instead simply :0.0, seems to help and indeed, xdvi and gv are working again here. So this appears to me like a new introduced bug in the shared memory handling? (Or am I wrong that the difference between :0.0 and <hostname>:0.0 is the way IPC between X-Server and -Client ist handled ?) Has something substantially been changed there, about 2 weeks ago ? Henry -- // // Do you suffer from long term memory loss ? I don't remember:-( // // Henry Vogt (henry@BA-Stuttgart.De) // Goethestr. 12, 71672 Marbach (Neckar), Tel. 07144/841653 // 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?199807171413.QAA02990>