Duplicated keystrokes on broadcast mode

[Herbert]

Hi,

I'm using Terminator 1.90-0~1694~ubuntu16.04.1 with English US (international, with dead keys) keyboard layout. With this layout I have to press SPACE after single-quotes or double-quotes, to get the quote, which is standard.

Terminator is duplicating the quotes when broadcast mode is On, using such keyboard layout.

As a quick fix, I'm using the English US (non international) layout only on Terminator, but sometimes I have to switch back to type some accented characters.

thanks in advance,

Herbert

[Stephen Boddy (stephen-j-boddy)]

I take it you mean that the active terminal gets the single character, and all the receivers get the character twice?

Honestly the input system, and getting broadcast to work for all situations is a bit of a nightmare. I think this might need quite a deep dive to figure out even *if* we can fix this. It depends on what the numerous key events look like, and if it is possible to ignore some of them, without fouling the broadcast up for all the other cases.

[Stephen Boddy (stephen-j-boddy)]

Hmm. I just tested the head with the same us dead key layout, and I get a single character in the receiving terminals too. Are you using some input subsystem like xim or something? It might help if you describe your distro, desktop, and anything unusual (i.e. not a plain vanilla Ubuntu install using a normal input method and keyboard map.)

[Herbert (herbert-fischer)]

The problem seems to be gone with 1.90-0~1739~ubuntu16.04.1.

[Stephen Boddy (stephen-j-boddy)]

I'll take the win, I'm not proud :-)

Marking as ummmmmm.... Fix Committed. Presumably we did *something* that changed the behaviour!

[qqchose (qqchose)]

Hello,
I regret to announce you that I have the same issue on Terminator 1.91-1, Ubuntu 18.10 :/
It does happen most of the times, though not always, and I was not able to find what triggers it.
I have a French keyboard.

[Patric (patric-bechtel)]

Can confirm that - the bug is back on 18.10 w/ 1.91-1.
German keyboard here. Tried with US English keyboard, but doesn't help.

[Patric (patric-bechtel)]

I may add: this happens with *every* key, not just the accent ones. So currently, on Ubuntu 18.10, this feature isn't usable at all.

[Massimo S. (smassimo)]

I have found that is something in the environment that cause the problem (I have Ubuntu 18.10 and the bug affect every key, as Patric)

If I start terminator with empty environment (except DISPLAY), it works!

env -i DISPLAY=:0 terminator

[Massimo S. (smassimo)]

It is the "GTK_IM_MODULE" environment variable (in my system it is GTK_IM_MODULE=ibus)

If I usent GTK_IM_MODULE, terminator works without the bug

env --unset=GTK_IM_MODULE terminator

[sky_walkie (hrdlo)]

same here; removing env var GTK_IM_MODULE=ibus helps.

[izzyb (izzyb)]

Having the same issue. Unsetting GTK_IM_MODULE seems to have no effect. I noticed in the redhat bug report someone noticed it doesn't happen when you sudo terminator, which I've confirmed.

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux bullseye/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

$ uname -a
Linux ibws 5.2.0-3-amd64 #1 SMP Debian 5.2.17-1 (2019-10-06) x86_64 GNU/Linux

$ terminator --version
terminator 1.91

Hope this is helpful. Would love to have this fixed. Thanks.

[brian mullan (bmullan)]

On ubuntu the following script fixed it for me permanently. Now broadcast all works w/out duplicating characters:

#!/bin/bash

sudo mv /usr/bin/terminator /usr/bin/terminator.SAVE
cat <<TERMINATOR > /tmp/terminator
sh -c "DBUS_SESSION_BUS_ADDRESS='' /usr/share/terminator/terminator"
TERMINATOR
chmod 755 /tmp/terminator
sudo mv /tmp/terminator /usr/bin

[Rafael Torres (rdtorres)]

I can confirm that unseting the DBUS_SESSION_BUS_ADDRESS env as advised by Brian solves the issue.

$ /usr/share/terminator/terminator -version
terminator 1.91

$ uname -a
Linux xxxxxx 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

[Martin Ruskov (mapto)]

A solution that worked for me was proposed on AskUbuntu: https://askubuntu.com/a/1337461/107990
The deletion of environmental variables worked for me previously, but not now on a different system.