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
Next revisionBoth sides next revision
terminator_vs_ubuntu_18.10_-_broadcast_issue [25.02.2019 10:43] – [Solution] Pascal Suterterminator_vs_ubuntu_18.10_-_broadcast_issue [29.03.2021 07:52] – Pascal Suter
Line 1: Line 1:
-====== terminator vs ubuntu 18.10 - broadcast issue ======+====== terminator vs ubuntu 18/20 - broadcast issue ======
 terminator is a very good graphical terminal emulator for linux. Its main advantage is that it allows to split the screen into several terminal windows and add tabs with additional split screens. On top of that, on can broadcast from one terminal to others.  terminator is a very good graphical terminal emulator for linux. Its main advantage is that it allows to split the screen into several terminal windows and add tabs with additional split screens. On top of that, on can broadcast from one terminal to others. 
 ===== Problem ===== ===== Problem =====
 There is an issue with broadcasting in ubuntu 18.10 with its standard desktop environment. every key that is pressed in the sending terminal is written twice in the receiving ones.  There is an issue with broadcasting in ubuntu 18.10 with its standard desktop environment. every key that is pressed in the sending terminal is written twice in the receiving ones. 
 +===== Reason =====
 +somehow terminator seems to have issues when ibus is involved
 ===== Solution ===== ===== Solution =====
 +we need to make sure that terminator does not use ibus. this is done differently in ubuntu 18 and ubuntu 20: 
 +
 +==== ubuntu 18 (tested with 18.10 but should also work with 18.04) ====
 as pointed out in [[https://bugs.launchpad.net/terminator/+bug/1318542/comments/26|a comment on a but report]] related to this issue, one can  unset the ''GTK_IM_MODULE'' environment variable prior to starting terminator which will work around the problem.  as pointed out in [[https://bugs.launchpad.net/terminator/+bug/1318542/comments/26|a comment on a but report]] related to this issue, one can  unset the ''GTK_IM_MODULE'' environment variable prior to starting terminator which will work around the problem. 
  
 +==== ubuntu 20.04 ====
 +here we need to unset ''DBUS_SESSION_BUS_ADDRESS'' for terminator to work correctly
 +
 +==== the script: ====
 the problem with the proposed alias is, that this only works if you start terminator through a bash shell. however, if you click the launcher icon in gnome it is ignored. the problem with the proposed alias is, that this only works if you start terminator through a bash shell. however, if you click the launcher icon in gnome it is ignored.
  
Line 11: Line 20:
 <code bash /usr/local/bin/terminator> <code bash /usr/local/bin/terminator>
 #!/bin/bash #!/bin/bash
-date>/tmp/test 
 GTK_IM_MODULE= /usr/bin/terminator GTK_IM_MODULE= /usr/bin/terminator
 +DBUS_SESSION_BUS_ADDRESS=""
 </code> </code>
 +don't forget to make it executable :) 
 +  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. 
  
  • terminator_vs_ubuntu_18.10_-_broadcast_issue.txt
  • Last modified: 28.12.2021 13:07
  • by Pascal Suter