From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42155) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXlw1-0008WL-NH for qemu-devel@nongnu.org; Mon, 22 Feb 2016 03:33:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aXlvy-0005gx-HA for qemu-devel@nongnu.org; Mon, 22 Feb 2016 03:33:37 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46088) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXlvy-0005gs-Bu for qemu-devel@nongnu.org; Mon, 22 Feb 2016 03:33:34 -0500 Message-ID: <1456130012.29896.28.camel@redhat.com> From: Gerd Hoffmann Date: Mon, 22 Feb 2016 09:33:32 +0100 In-Reply-To: <56CA1FCE.9040308@web.de> References: <1450356422-31710-1-git-send-email-pbonzini@redhat.com> <20160217135340.GF29494@noname.str.redhat.com> <56C47E12.4000007@redhat.com> <56CA1FCE.9040308@web.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] gtk: implement set_echo List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Kevin Wolf , Paolo Bonzini , qemu-devel@nongnu.org On So, 2016-02-21 at 21:36 +0100, Jan Kiszka wrote: > On 2016-02-17 15:05, Paolo Bonzini wrote: > >=20 > >=20 > > On 17/02/2016 14:53, Kevin Wolf wrote: > >> Waiting didn't fix the bug, so I tried a git bisect now and it pointed > >> me to this commit. > >> > >> I'm using HMP with the default vc backend. Starting with this commit, > >> the echo is broken sometimes, in a way that the first character in the > >> entered command is duplicated for each new character I enter, like thi= s: > >> > >> (qemu) ii > >> (qemu) iiin > >> (qemu) iiiinf > >> (qemu) iiiiinfo > >> > >> This doesn't happen always, but often enough to be annoying. > >=20 > > The patch for it is already on the way. >=20 > Is it still on the road, or did it already arrive on the list at least? > I just bisected to this bug as well and would be happy to see this fixed. Pull req just sent. cheers, Gerd