keyboard input was recognized two times in broadcast group mode

[mumeiyamibito]

Ex.
Terminal 1 and 2 were same group and synchronized by broadcast mode.
I entered command 'ls' on Terminal 1.
Terminal 2 displayed 'llss'.
When I hit 'Enter' key, Terminal 1 displayed list of files in current directory and Terminal 2 said "No command 'llss' found".

This problem has occured Terminator (0.98+1707~ubuntu14.04.1, 0.98~ppa6, 0.97-2ubuntu0.1, and 0.97-2) in LinuxMint 17.3 (64 bit). Furthermore, it also occured without config file.

[Stephen Boddy (stephen-j-boddy)]

Please take a look through https://bugs.launchpad.net/terminator/+bug/1318542

I keep seeing this bug, and coming up with workarounds and improvements, but as stated in that bug, Linux Input is a nightmare due to all the variations.

There I committed a fix, but no one responded to the last request for feedback. You seem to have the latest nightly containing what I thought was the final fix, but now we have to go through troubleshooting again, and try not to break things for everyone else.

Standard questions:
Do you use IBus, or something else for changing keyboard layouts, or for non ascii-char input? These tend to do funky things to the keyboard events that mess up broadcast.
What language/region is your system set for? It may have a bearing, although it shouldn't.

The more info you can provide on this area, the easier it is to diagnose and/or workaround.

Comment 17 in that bug provides instructions for running a debug branch that would give me good feedback (and shouldn't disrupt your normal install).

[mumeiyamibito (mumeiyamibito)]

Hi, Stephen Boddy.

I use input method named fcitx (like iBus) and my locale is Japanese.

You're right.
When I tried to turn off this input method, this problem does not occured.
I have used fcitx or iBus on LinuxMint 17, 17.1, 17.2 but this problem have not occured.
And it have not occured on Ubuntu 15.10 Japanese Remix, which use fcitx.

So, this problem may have been caused by fcitx on LinuxMint 17.3 (cinnamon) 64bit.

[Stephen Boddy (stephen-j-boddy)]

For IBus there was an env var we could set if we detect it that stops it interfering with input:
http://bazaar.launchpad.net/~gnome-terminator/terminator/trunk/revision/1611
http://bazaar.launchpad.net/~gnome-terminator/terminator/trunk/revision/1647

The IBus dev was pretty good providing help and feedback. This is the first time I've encountered fcitx, so it is at the moment unclear how (or if) we can fix this in Terminator.

I take it fcitx is an essential piece of your environment? If so, we'll need to figure out a way of working around whatever it is that fcitx is doing. To progress further I'd really need the output from the branch described in comment 17 of LP:1318542, ideally with fcitx running, and also without fcitx running. I can then request some help from the fcitx devs to figure out the best way to stop fcitx doing odd things in the event queue.

[Florian Röser (florian.roeser)]

Hi, I experienced this since Ubuntu 18:10
It does not occur in Ubuntu 18:04 LTS

I just freshly installed Ubuntu 19:04 and experience the same issue.
Locale: en_US
using a pretty fresh Ubuntu 19:04 Desktop installation.
Also I'm using 'oh-my-zshell' instead of bash.

[James O'Cull (jocull)]

Happening to me in Pop!_OS 19.04 (which is an Ubuntu 19.04 base). This is a nearly fresh installation (day 2). I'm using Fish shell (with oh-my-fish), but it doesn't seem to fix anything if I switch to bash.

What can I do to help debug? :)

[Alon Diamant (advance512)]

Can confirm this happens on Ubuntu 19.10 with version 1.91-4 installed via apt-get.

[h (h1234567ok)]

hello.

I would strongly recommend against "fixing" this bug, until the ridiculous default keybinding (Alt-A) is completely removed.

This 'broadcast' feature, has such risk of damage, that it should not have any default keybinding.

I have been using Terminator for years now, yet I was just struck by the 'broadcast' feature. It does explain a few weird occurrences in the past.

I had 16 terminals, showing various sessions logged in across 3 servers, some of them as root.

It seems somehow, (I guess) I accidentally typed Alt-A in one terminal.

Since then every character I then typed was being sent as input in every terminal.

I was typing, for example, in one terminal, things such as 'rm -f *', 'rm -f x*' and so on.

this "Bug" saved me because in all those other terminals, instead of 'rm -f *' it was running 'rrmmff --ff **'

All users of Terminator should consider removing the default keybinding, by setting them to None in ~/.config/terminator/config, for example:

$> cat ~/.config/terminator/config
[global_config]
[keybindings]
  help = None
  broadcast_all = None
  broadcast_group = None

Fortunately I'm very happy right now, thanks to this "bug", that I didn't lose a bunch of files, across a bunch of directories, on a bunch of servers.

[Fabrice Moyen (fmoyen)]

I have the same issue with terminator-1.92-3.fc31.noarch.
I've read that ibus was the root cause of this broadcast "double" effect and indeed I have ibus running. I've killed ibus process and yes broadcast terminator functionality started working but... yakuake I'm using in parallel stopped working... So it seems I need ibus. I've had a look at /usr/bin/terminator python3 script and there is a workaround coded inside for ibus interfering with broadcast (that's what is written in the script) but I don't know python so difficult for me to try and solve this workaround issue. Any clue ?