From owner-freebsd-x11@FreeBSD.ORG Sat Apr 30 19:35:58 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 F3A1316A4CE for ; Sat, 30 Apr 2005 19:35:57 +0000 (GMT) Received: from mail-in-02.arcor-online.net (mail-in-02.arcor-online.net [151.189.21.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E114E43D1D for ; Sat, 30 Apr 2005 19:35:56 +0000 (GMT) (envelope-from mailnull@mips.inka.de) Received: from kemoauc.mips.inka.de (dsl-084-056-231-081.arcor-ip.net [84.56.231.81]) by mail-in-02.arcor-online.net (Postfix) with ESMTP id F22FA139632 for ; Sat, 30 Apr 2005 21:35:54 +0200 (CEST) Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.13.3/8.12.10) with ESMTP id j3UJZq5q018378 for ; Sat, 30 Apr 2005 21:35:52 +0200 (CEST) (envelope-from mailnull@kemoauc.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.13.3/8.13.1/Submit) id j3UJZqlg018377 for freebsd-x11@freebsd.org; Sat, 30 Apr 2005 21:35:52 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Date: Sat, 30 Apr 2005 19:35:51 +0000 (UTC) Message-ID: Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-x11@freebsd.org Subject: 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:35:58 -0000 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? -- Christian "naddy" Weisgerber naddy@mips.inka.de