Bug#761671: gnome-terminal: Keypress lagging by one character

[Conrad Hughes]

Pedro> Sorin and Conrad, could you please still reproduce this issue
Pedro> with newer version of libvte-2.91-0 and gnome-terminal ?

It gradually faded away for me shortly after I reported the bug: I can't
remember encountering it recently at all.  Currently on:

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name           Version      Architecture Description
  +++-==============-============-============-=================================
  ii  libvte-2.90-9  1:0.36.3-1   amd64        Terminal emulator widget for GTK+
  ii  libvte-2.90-co 1:0.36.3-1   all          Terminal emulator widget for GTK+
  ii  libvte-2.91-0  0.38.1-1     amd64        Terminal emulator widget for GTK+
  ii  libvte-2.91-co 0.38.1-1     all          Terminal emulator widget for GTK+
  ii  libvte-common  1:0.28.2-5   all          Terminal emulator widget for GTK+
  ii  libvte9        1:0.28.2-5   amd64        Terminal emulator widget for GTK+
  ii  gnome-terminal 3.14.1-1     amd64        GNOME terminal emulator applicati
  ii  gnome-terminal 3.14.1-1     all          Data files for the GNOME terminal

.. I think the barest hint of it may still be present, in that I still
notice when starting vim that terminal control sequences sometimes show
up half-completed on screen as text (so it's a bit of a mess at the
bottom of the screen, and the cursor doesn't move to the top until you
type "i", but things clear up once you do that).

Pedro> If so, is the same behavior as
Pedro> https://bugzilla.gnome.org/show_bug.cgi?id=730763 like Egmont reported ?

They could amount to the same thing, but I can't test this.  I did
hypothesise that it could be display lag rather than input lag in my
original report.  I never got a chance to thoroughly test this though.

Regards,
Conrad