From owner-freebsd-x11@FreeBSD.ORG Sat Apr 30 19:43:13 2005 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79C7D16A4CE for ; Sat, 30 Apr 2005 19:43:13 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00A8543D1F for ; Sat, 30 Apr 2005 19:43:13 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.50 (FreeBSD)) id 1DRxrt-0004es-54; Sat, 30 Apr 2005 21:43:13 +0200 Date: Sat, 30 Apr 2005 21:43:13 +0200 From: Kirill Ponomarew To: Christian Weisgerber Message-ID: <20050430194313.GC17052@voodoo.oberon.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE Keywords: 579279786 cc: freebsd-x11@freebsd.org Subject: Re: xterm stops output X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2005 19:43:13 -0000 On Sat, Apr 30, 2005 at 07:35:51PM +0000, Christian Weisgerber wrote: > FreeBSD 5.4-STABLE/alpha, xterm-201. > > Lately I suffer from the problem that xterm very sporadically appears > to stop output, possibly until a key is pressed. This is not readily > reproducible and overall very rare. It seems to happen comparatively > often in trn. Half a screen is painted and then output just stops. > I need to hit a key, usually ^R for repainting, to get a proper > display. It has also happened for non-curses cases, such as the > output of ifconfig. Never in vi. > > I have not payed too much attention yet, since it occurs only > sporadically, I'm usually eager to continue with what I was doing, > and it took me a while to realize that there really is an issue. > In fact, I'm still not certain there is. > > If my memory serves correctly, this has started since I upgraded > from xterm-200 to xterm-201. > > Is anybody else seeing unusual behavior from xterm? Yup, it's known problem, will be fixed soon in oncoming 202 release. -Kirill