From owner-freebsd-stable@freebsd.org  Wed Jan 25 10:24:59 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6749CBF181
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 25 Jan 2017 10:24:59 +0000 (UTC)
 (envelope-from emz@norma.perm.ru)
Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (Client CN "mail.norma.perm.ru",
 Issuer "Vivat-Trade UNIX Root CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4732B17B3
 for <freebsd-stable@freebsd.org>; Wed, 25 Jan 2017 10:24:58 +0000 (UTC)
 (envelope-from emz@norma.perm.ru)
Received: from bsdrookie.norma.com. ([IPv6:fd00::7af])
 by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id v0PAOtBl067650
 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <freebsd-stable@freebsd.org>; Wed, 25 Jan 2017 15:24:55 +0500 (YEKT)
 (envelope-from emz@norma.perm.ru)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=norma.perm.ru; s=key;
 t=1485339895; bh=2Bv3cQxh5XHmzSKBFrpqKUP8ctpg9+nA/anX5d2KW2I=;
 h=Subject:References:To:From:Date:In-Reply-To;
 b=t4lUsRnoqnxN+gvCA5F5rOAH7SbVBnBagpgY2t/IQTUPQ0QbDgQqsJHhOg2m4yTg8
 yGagcWyvL40vB5FX4hoNouNo6xne5uuU2lpn6Hnoe/f6I7rEt+OR8RJFHFYcI8phy6
 FMHpfIBMr3ZQkb/q/D3oiGvupgVbS3y7tD7jR9MA=
Subject: Re: reset not working like 70% of the time
References: <5888754F.2040901@norma.perm.ru>
 <20170125101517.GW13006@home.opsec.eu>
To: freebsd-stable@freebsd.org
From: "Eugene M. Zheganin" <emz@norma.perm.ru>
Message-ID: <58887CF7.1010908@norma.perm.ru>
Date: Wed, 25 Jan 2017 15:24:55 +0500
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <20170125101517.GW13006@home.opsec.eu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jan 2017 10:25:00 -0000

Hi.

On 25.01.2017 15:15, Kurt Jaeger wrote:
> 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... ?
>
A typical cases are:

- newlines aren't working properly, current line just got cleaned and
that's all (no scrolling up one line happens)
- mouse clicking produces some input symbols in the terminal line
- Ctrl-C stops working (just nothing happens)

I'm seeing all of these in my konsole terminal window while working with
local and remote hosts (mostly with remotes), an typing 'reset' usually
just does nothing. God bless the Midnight Commander !

Eugene.