terminator_vs_ubuntu_18.10_-_broadcast_issue

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
terminator_vs_ubuntu_18.10_-_broadcast_issue [29.03.2021 07:55] – [the script:] Pascal Suterterminator_vs_ubuntu_18.10_-_broadcast_issue [08.05.2026 14:46] (current) – [Thinlinc] Pascal Suter
Line 20: Line 20:
 <code bash /usr/local/bin/terminator> <code bash /usr/local/bin/terminator>
 #!/bin/bash #!/bin/bash
-DBUS_SESSION_BUS_ADDRESS="" GTK_IM_MODULE= /usr/bin/terminator+DBUS_SESSION_BUS_ADDRESS="" GTK_IM_MODULE="" /usr/bin/terminator
 </code> </code>
 don't forget to make it executable :)  don't forget to make it executable :) 
-  chmod 755 /usr/local/bin/terminator''+  chmod 755 /usr/local/bin/terminator
  
 the reason why this is saved to ''/usr/local/bin'' is, that this directory is listed in the ''PATH'' variable before ''/usr/bin'' is listed where the actual terminator binary resides. hence, when someone starts terminator wihtout providing a full path, our wrapper script will be launched first.  the reason why this is saved to ''/usr/local/bin'' is, that this directory is listed in the ''PATH'' variable before ''/usr/bin'' is listed where the actual terminator binary resides. hence, when someone starts terminator wihtout providing a full path, our wrapper script will be launched first. 
Line 30: Line 30:
  
 we could have also renamed the actual binary and then saved the wrapper in its place, or we could have modified the launcher file, but both of these solutions will probably brake on each update of terminator, while our little hack, although not pretty, will survive updates as well.  we could have also renamed the actual binary and then saved the wrapper in its place, or we could have modified the launcher file, but both of these solutions will probably brake on each update of terminator, while our little hack, although not pretty, will survive updates as well. 
 +
 +===== Other problems =====
 +==== Thinlinc ====
 +if you are using thinlinc to connect to your linux machine, thinlinc will not source ''/etc/environment'' to start building the ''PATH'' variable but it will use its own initial calue for ''PATH'' as defined in ''/opt/thinlinc/etc/conf.d/vsmagent.hconf'' and unfortunately by default it will check ''/bin'' before ''/usr/bin/local'' which makes the above script useless. the simplest solution is to adjust the order of directories in that config file so taht ''/usr/local/bin'' is checked first. here is an example, what a working PATH may look like in ''vsmagent.hconf''
 +  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/thinlinc/bin:/usr/bin/X11
 +
 +after changin this, you need to completely end your remote gnome session and start a new one for this change to take effect.
 +
 +==== split-screen shortcut ctrl+shift+e not working ====
 +if terminator works with ibus active, you can experience a strange behaviour when using the ctrl+shift+e shortcut to split screens: you will get an underlined "__e__" and the terminal behaves strange until you press escape. this is because this same shurtcut is used by ibus to write emojis. you can change the ibus shurtcut by running 
 +  ibus-setup
 +then go to the emoji tab and either change or remove the shortcut
 +
  • terminator_vs_ubuntu_18.10_-_broadcast_issue.1616997331.txt.gz
  • Last modified: 29.03.2021 07:55
  • by Pascal Suter