Broadcasting input across multiple terminator windows repeats keypresses many times

Bug #819775 reported by Max Bowsher
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
terminator (Arch Linux)
New
Undecided
Unassigned
terminator (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

To reproduce:

Start terminator
Create a new window (Shift-Ctrl-I in default keybindings)
Select "Broadcast all" mode (via the top-left terminator dropdown)
Type anything

The keypress is repeated very many times.

The following output is emitted on the stderr of the terminator process:

Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 48, in apport_excepthook
    if not enabled():
  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 21, in enabled
    import re
RuntimeError: maximum recursion depth exceeded while calling a Python object

Original exception was:
Traceback (most recent call last):
  File "/usr/share/terminator/terminatorlib/terminal.py", line 726, in on_keypress
    mapping = self.terminator.keybindings.lookup(event)
RuntimeError: maximum recursion depth exceeded

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: terminator 0.95-1 [modified: usr/share/applications/terminator.desktop]
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
Date: Tue Aug 2 12:55:45 2011
EcryptfsInUse: Yes
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: terminator
UpgradeStatus: Upgraded to natty on 2011-04-14 (109 days ago)

Revision history for this message
Max Bowsher (maxb) wrote :
Revision history for this message
Tom Smith (takeontom) wrote :

Am unable to replicate this on quantal.

$ lsb_release -rd
Description: Ubuntu quantal (development branch)
Release: 12.10

$ apt-cache policy terminator
terminator:
  Installed: 0.96-0ubuntu1
  Candidate: 0.96-0ubuntu1
  Version table:
 *** 0.96-0ubuntu1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ quantal/universe amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Martin Meredith (mez) wrote :

Could you please check whether this problem still exists for you in the latest version of ubuntu ? As this has been reported against an older version of Ubuntu, it'd be nice to see whether it still exists.

Till then, I'll mark this as incomplete.

Changed in terminator (Ubuntu):
status: New → Incomplete
Revision history for this message
Max Bowsher (maxb) wrote :

I can't even reproduce it in precise - assuming it got fixed in either oneiric or precise and closing bug.

Changed in terminator (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Samir Ibradžić (sibradzic) wrote :

Not fixed! The problem is reproducable ONLY if one is running IBUS.

samir@nigdje:~$ lsb_release -rd
Description: Ubuntu 12.10
Release: 12.10

samir@nigdje:~$ apt-cache policy terminator
terminator:
  Installed: 0.96-0ubuntu1
  Candidate: 0.96-0ubuntu1
  Version table:
 *** 0.96-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ quantal/universe amd64 Packages
        100 /var/lib/dpkg/status

Needles to say,

killall ibus-daemon

makes it disappear...

Btw, IBUS in Ubuntu is in a crappy state, too old versions are being shipped with each release... Do are you missing devs who actually use it and test it?

If i have any time left, I'll try to dive into terminator code to find the culprit...

Revision history for this message
Max Bowsher (maxb) wrote :

Oh, *right*, so that's why the problem disappeared for me. I remember purging ibus from my system at one point, since I never use it at all.

Changed in terminator (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Bruno Lambert (bruno.lambert) wrote :

Just tested in 14.04: the bug is still present. apt-get purge ibus ; killall ibus-daemon "fix" the issue.

Revision history for this message
Lukas Vacek (lukas-vacek) wrote :

looks like a bug in libvte 0.28.2 - key-press-event (callback is on_keypress in terminal.py) is triggered twice

Revision history for this message
Lukas Vacek (lukas-vacek) wrote :

A quick patch (a really quick workaround) attached - it probably messes up broadcasting when the ibus is *not* installed.

But it fixes the double broadcasting in the default install.

To apply:

apt-src install terminator
cd terminator
export QUILT_PATCHES=debian/patches
export QUILT_REFRESH_ARGS="-p ab --no-timestamps --no-index"
quilt push broadcast_double_with_ibus_workaround.diff
dpkg-buildpackage
cd ..
sudo dpkg -i terminator_0.97-4_all.deb

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "broadcast_double_with_ibus_workaround.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

The fact is that input is horribly complex and we're doing something particularly unusual with broadcasting. It's a miracle it works as well as it does. Have you tested a recent nightly? A number of fixes went in to try to get broadcasting working in all cases (w/IBus, wo/IBus, setkeymap.) If you still see the double char (or can temporarily induce it, please try a nightly and report back if the double char is fixed for all conditions,

Revision history for this message
Rodrigue ROYER (rodrigue-royer) wrote :

Hello there. I'm using lubuntu with lxde desktop and I'm experiencing this double char bug.
I've tried the GTK3 branch and also the "lp" branch witch I suppose to be the nighty build you talking about. And the bug is still here. I can confirm that kill ibus resolve the problem but it break other things elsewhere so I cannot use this as a workaround.

Revision history for this message
Nybble (wuxb45) wrote :

I consistently experience this issue and it's still here for recent releases (1.91).

Does anyone know how is the progress of the fixing?

Revision history for this message
Ben Reaves (rbreaves) wrote :

I am also experiencing this issue on GalliumOS (Ubuntu with XFCE, 16.04, Xenial release).

Not sure yet what causes it, but it has occurred 3 times now and restart the app does resolve it, for awhile any ways. This is a pretty serious issue. I log into multiple systems, so having a terminal that I do not have to worry about bleeding input on is pretty critical. May have to find an alternative that is more reliable, which is sad because I have found how to configure this terminal perfectly in every other respect.

Revision history for this message
cherepanov (a-cherepanov) wrote :

I constantly have this issue.
After a while input is cloned between all consoles.
If I close and reopen terminal everything fine for some time.
Ubuntu 16.04-17.10, terminator 1.91 Ubuntu and nightly versions on fresh Ubuntu.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.