Comment 8 for bug 1758564

I'm on Terminator 1.91-1 and Ubuntu Linux 18.10 (cosmic) and had the same issue.

To fix this, I followed the aforementioned advice. However, I also cleaned up all the .pyc files and __pycache__ and forced a complete recompile.

Finally, note that the aforementioned solution contains a typo: It is "custom_commands.py", NOT "customer_commands.py"! ;)

As the solution does not seem to work for everyone. I am assuming that it is due to different file locations, the typo, and potentially a lack of properly cleaning up the Python byte code files.

Here's the complete procedure step-by-step as it worked for me:

1) Find out where your terminator files are and cd to that directory:
which terminator
    // Output: /usr/bin/terminator -> ../share/terminator/terminator
    // So the terminator root directory is /usr/share/terminator in this case

2) cd /usr/share/terminator

3) Change custom_commands.py as indicated by others

sudo nano terminatorlib/plugins/custom_commands.py

Change line 130 of terminatorlib/plugins/custom_commands.py

from:

terminal.vte.feed_child(command, len(command))

to:

terminal.vte.feed_child(command)

4) sudo pyclean . // To be on the safe side. Alternatively, use: sudo py3clean .
5) sudo python -m compileall . // Re-compile the whole lot
6) restart terminator // <-- This is necessary!

Custom commands should now work. To test, select and run a custom command from the commands menu.