Upgraded 21.10 to 22.04, input is doubled on broadcast windows

[kellyschoenhofen]

Describe the bug
Upgraded 21.10 to 22.04, input is doubled on broadcast windows.

To Reproduce
Open Terminator, split horizontally, broadcast all, press a key. One shows up in the foreground window, two shows up in the split window.

Expected behavior
The same number of characters are broadcast as entered.

Desktop:

• Ubuntu
• 22.04
• X11

[mattrose]

What version of terminator are you running?

if you run under terminator -u does that fix the problem?

[kellyschoenhofen]

My apologies, I should have included the version.

$ sudo apt-cache policy terminator
terminator:
  Installed: 2.1.1-1
  Candidate: 2.1.1-1
  Version table:
 *** 2.1.1-1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu jammy/universe i386 Packages
        100 /var/lib/dpkg/status

terminator -u didn't change the behavior, the non-infocus broadcast windows have the doubled chars.

[mattrose]

Ugh, can you check out master and see it if has the same problem? I think we've done some work on that since the last release.

[kellyschoenhofen]

OK, I tried, I think I did what you asked.
I couldn't tell if I was really using terminator from the repo, so I uninstalled terminator (e.g. sudo apt remove terminator) and I'm 100% sure when I did 'python3 terminator' it was running the one I cloned from github. I did have to put back a few dependencies though,

sudo apt install python3-psutil python3-configobj gir1.2-keybinder-3.0 libkeybinder-3.0-0

and yes, non-primary broadcasted windows had doubled chars.

Then I wanted to build it and see if the same thing happened, I believe I also needed to install intltool and gettext so successfully build it, but it built and I replaced the terminator and remotinator from the build/scripts-3.10/ folder, and the same issue still persisted, doubled chars.

This was a 21.10 desktop upgraded to 22.04, I'll spin up a 22.04 vm fresh from the iso and see if this occurs.

[mattrose]

OK, there are a few things we can try to get this working. It's conflicting with ibus-daemon for some reason, and we keep trying to work around it, and it seems to keep breaking in new and wonderful ways.

[ros-financial-com]

I'd just like to add that I experience the same behaviour on ArchLinux 5.17.6-arch1-1 with terminator 2.1.1-3 in gnome-shell 1:42.1-1. I hope this might be helpful.

[dreamonhigh]

same issue on Ubuntu 22.04
I can read my passphrase in cleartext on different windows. with double characters.
Terminator is not useable anymore :(

[mattrose]

I've tried to install a VM with Ubuntu 22.04 with not much success, if anyone can go through the troubleshooting steps in #78 and #504, and report the results, that would help resolve this much quicker.

[Ajk4]

Leaving info for others.

I tried everything posted online on Ubuntu 22.04 and nothing works.

What finally worked for me was disabling Wayland like described in this article https://linuxconfig.org/how-to-enable-disable-wayland-on-ubuntu-22-04-desktop

[kellyschoenhofen]

OK, I tried a few things. Switching to gnome/x11 how the prior comment linked to did not change the doubled input behavior.
Trying what was in #78 and #504,

export IBUS_NO_SNOOPER_APPS=python3 

Did not change doubled behavior

But,

export DBUS_SESSION_BUS_ADDRESS=$(dbus-launch)
# technically "fixed" the issue, it overwrote the prior:
DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1911838151/bus"
# to this:
DBUS_SESSION_BUS_ADDRESS="DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-fxgffHu2tm,guid=5b5807194ad75ceca08669a462b61759

Which now resulted in this output when I launched terminator:

$ terminator 
Unable to connect to DBUS Server, proceeding as standalone

but doubled behavior stopped/was fixed.

Edit: did not mean to close this, mis-click, my apologies. Reopened.

[kellyschoenhofen]

OK - that export dbus_session seemed obviously malformed, so poking around, it seems on 22.04 export $(dbus-launch) is the correct command to set it. Doing that resulted in a manual terminator launch that:

1. didn't throw a warning/error that it was unable to connect to DBUS Server,
2. and fixed the doubled input on broadcast issue

Setting it with just export $(dbus-launch) also updated the pid value correctly, e.g.

$ export
declare -x DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-fAFPL65H0a,guid=a5fa200a99c760c8beb5a22c62b61ca0"
declare -x DBUS_SESSION_BUS_PID="19967"

[mattrose]

Has anyone opened a bug with Ubuntu about this? It seems that Ubuntu is the only distro that is having these problems, and I think it's something to do with their weird mix of Gnome 41 and 42 and their extensions.

[mattrose]

I finally got an ubuntu 22.04 desktop and am unable to reproduce this

[mattrose]

After some consideration, I'm going to close this bug now, as I can't figure out what to do next. Please re-open if you can find a way for me to reproduce this

[dreamonhigh]

Hallo.

[dreamonhigh]

Sorry, I've forgotten.
I tried once more. start terminator. make "tile horizontal". make another terminator open(move it to the right), and do again "tile horizontal".
type some text in upper left tiled window .. look in other windows .. output is twice shown in 3 other tiled terminator instance.

I did not tried in a new installation. If you still can not reproduce I will make a new installation and try again.

One more thing. the upper 2 windows are from ubuntu 22.04 apt install terminator, and lower both are from git version. I downloaded like you told and started the git clone... there have to be 2 running terminators

Wondering that you could not reproduce. starting 2 terminators and typed left 123 prints right side 112233. typing right 56789 it prints left 5566778899. STRANGE

Hope this helps.

[dreamonhigh]

Ok, installed now 22.04 in Virutalbox. The problem is not there. Im confused. In real system it happens everytime I starte 2 terminator windows.
I will go asking in some #ubuntu irc if they can reproduce this issue.

[dreamonhigh]

maybe there are old configs, that conflict after upgrading to 22.04?
I purged terminator and removed ./config/terminator .. maybe there is more to delete?

I think its the only way that might be the reason. cause new installation of system works without that issue.

[mattrose]

There is a very small chance that there is a config in /etc/xdg/ or in a directory in the XDG_CONFIG_DIRS array. More likely that there is still a terminator window running under the old config. Make sure that there are no terminator sessions running (using ps auxw | grep terminator or something similar) before restarting. Sometimes terminator sessions can hang around and will re-use the old config unless you stop ALL of the instances.

[dreamonhigh]

Thats it. Ok, there was no /etc/xdg config. but you were right, there was still a terminator process running. I removed .config/terminator and killed this process. started again. AND.. IT WORKS LIKE IT SHOULD. I removed config, so I cannot compare anymore. maybe I have a backup that I made a month ago. If you like, I would dig in there.
Im lucky to have terminator back again. ;)

[sailing0505]

I'm going to close this bug now, as I can't figure out what to do next. Please re-open i

This workaround works on my ubuntu 22.04. I was troubled for this problem for few days. Thank you.

[merabmali]

This bug occurred to me in WSL2. I don't know if this is relevant but my workaround was to switch off broadcasting in top left corner. Then behavior returns to normal.

[gouzhuang]

I can reproduce it easily with a fresh install of Ubuntu 22.04. The key is to use Xorg instead of Wayland. There is no problem in Wayland, but once I switch to Xorg, the problem shows up.

[yurenchen000]

I guess it's about input methods (at lease my ubuntu was),
I killed ibus (maybe also fcitx) to avoid it

[chenjiayi8]

I guess it's about input methods (at lease my ubuntu was), I killed ibus (maybe also fcitx) to avoid it

This is the only solution works for me.

[kimba74]

I guess it's about input methods (at lease my ubuntu was), I killed ibus (maybe also fcitx) to avoid it

This is the only solution works for me.

Same for me. Double characters show up only under X11 and are fixed by killing ibus.

[phong-phan]

I'm using ibus for input method, is there any chance to still keep ibus running and solve this issue? Thank you.

[yurenchen000]

I'm using ibus for input method, is there any chance to still keep ibus running and solve this issue? Thank you.

@letsgologan
I'm on ubuntu22 too,
just share a little experience
(if you don't want to roughly stop input-method)

for fcitx

//this will disable fcitx in terminator

GTK_IM_MODULE= terminator -u

#78 (comment)

for ibus

//ibus can work in terminator , but only broadcast eng input

IBUS_NO_SNOOPER_APPS=python3 terminator -u

#504 (comment)

[phong-phan]

Hi, thank you for the suggestion, i end up backup the /usr/bin/terminator into /usr/bin/terminator.back
and create a script called /usr/bin/terminator like this and set execution permission for it:

#!/bin/bash
sh -c "DBUS_SESSION_BUS_ADDRESS='' /usr/bin/terminator.back"

So far it been working as expected for me.
My os and version info:
OS: Ubuntu 22.04
Terminator version: 2.1.3

On my work PC, I had the same issue but probably in a older version of Terminator.
I've been able to fix it using the answer in this:
https://askubuntu.com/questions/1189243/why-is-terminator-sending-double-characters-to-terminals-that-arent-selected-in

But on Ubuntu 22 i can not find this file /usr/share/terminator/terminator anymore.
So far so good things been working as expected. Thank you

[mattrose]

O no I'm as e Wwxzxh I don't think that'll hold a play a conversation out hereow m trains are going hard grams are going no x> OK - that export dbus_session seemed obviously sxru hi xeu Oh god yeah I don't knows is not coming back to the road Xavier we x Cmalformed, so poking around, it seems on 22.04 export $(dbus-launch) is the correct command to set it. Doing that resulted in a manual terminator launch that:
#A new > C scum D

dhccuwc wxxxxxqxqcxqcdwd do

1. didn't throw a warning/error that it qwnn one was wsss ox I eeesqssssaarrcu yay Jen uciuiuxi I'm c I was a I scared dadx sqqss was unable to connect to DBUS Server,

2. and fixed the doubled input on broadcast issue

Setting it with just export $(dbus-launch) also updated the pid value correctly, e.g.

$ export

declare -x DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-fAFPL65H0a,guid=a5fa200a99c760c8beb5a22c62b61ca0"

declare -x DBUS_SESSION_BUS_PID="19967"

[Hoog2000]

This fixed the double char problem for me :)

ibus restart

[pedrofilhojp]

I fixed my terminator closing the ibus

ibus exit

[abacao]

I'm facing the same issue.
Tested all options without success.

When primary is 1 char, 2nd or 3rd windows is double char.

Running:

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"

$ terminator -v
terminator 2.1.1

#596 (comment)
Does not fix the problem.

DBUS and IBUS env

$ env | grep DBUS       
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
$ env | grep IBUS       
IBUS_DISABLE_SNOOPER=1

After export DBUS_SESSION_BUS_ADDRESS=$(dbus-launch)

$ env | grep DBUS                               
DBUS_SESSION_BUS_ADDRESS=DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-w7zo81jCgK,guid=f0115be7895589a799c9b14d652abb05
DBUS_SESSION_BUS_PID=1609509
DBUS_SESSION_BUS_WINDOWID=100663297

Still having the double char issue

@mattrose or @kellyschoenhofen

Can you guys please reopen this?

[gakutasu]

@abacao
The following worked on ubuntu20.04
test it please, and I hope it gets resolved

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