Date: Wed, 25 Jan 2017 11:15:17 +0100 From: Kurt Jaeger <lists@opsec.eu> To: "Eugene M. Zheganin" <emz@norma.perm.ru> Cc: freebsd-stable@freebsd.org Subject: Re: reset not working like 70% of the time Message-ID: <20170125101517.GW13006@home.opsec.eu> In-Reply-To: <5888754F.2040901@norma.perm.ru> References: <5888754F.2040901@norma.perm.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > does anyone suffer from this too ? Right now (and for several last > years) a 100% decent way to reset a terminal session (for instance, > after a connection reset, after acidentally displaying a binary file > with symbols that are treated as terminal control sequence, after > breaking a cu session, etc) is to launch midnight commander and then > quit from it. And the reset is working like in 30% of cases only. [...] > Am I the only person seeing this ? I had some cases in the past where xterm was hanging, too -- but not with *that* high rate of problems. Most of the times, xterm's Full Reset options works fine. The question is: how to debug that... ? -- pi@opsec.eu +49 171 3101372 3 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170125101517.GW13006>