Double characters on inactive terminal

Bug #1398424 reported by Carroarmato0
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
terminator (Ubuntu)
Confirmed
High
Unassigned

Bug Description

When opening multiple terminals (within the same session) and enabling "broadcast all" key strokes are being repeated multiple times.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: terminator 0.97-4
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 2 16:14:11 2014
InstallationDate: Installed on 2014-11-29 (3 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: terminator
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Carroarmato0 (carroarmato0) wrote :
Revision history for this message
Vuokko (vuokko-vuorinnen) wrote :

I can confirm this bug, after upgrading from ubuntu 14.04 (where this worked) to 14.10 I also got this bug

Revision history for this message
Pe Ku (masaj) wrote :

I've also experienced this, happens everytime.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in terminator (Ubuntu):
status: New → Confirmed
Revision history for this message
Pe Ku (masaj) wrote :

I tried to downgrade to the version 0.97-2ubuntu0.1 as used in Trusty, but didn't help.

Changed in terminator (Ubuntu):
importance: Undecided → High
Revision history for this message
Bert van der Horst (bert-vdrhorst) wrote :

Having the same issue on Ubuntu 14.10

Revision history for this message
LKP (lkernelpanic) wrote :

If I'm not mistaken, this is the same issue reported in bug: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/819775

The problem can be avoided by killing ibus-daemon or by going, in Unity, to System Settings -> Language Support and setting Keyboard input method system to none which won't start ibus-daemon on next restart

Doesn't fix the error though (the root cause why ibus and terminator can't play nicely with each other)

Revision history for this message
Raoul Scarazzini (rasca) wrote :

Same problem with Linux Mint 17.1 Rebecca (so Ubuntu 14.10), killing the ibus-daemon gives a workaround.

Revision history for this message
Egmont Koblinger (egmont-gmail) wrote :

See also bug 1518089.

Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

Please ignore Egmonts comment re lp:1518089 That has nothing to do with this.

The fact is that input is horribly complex and we're doing something particularly unusual with broadcasting. It's a miracle it works as well as it does. Have you tested a recent nightly? A number of fixes went in to try to get broadcasting working in all cases (w/IBus, wo/IBus, setkeymap.) If you still see the double char (or can temporarily induce it, please try a nightly and report back if the double char is fixed for all conditions,

Revision history for this message
Ahmad Amr (aamr) wrote :

This is appearing again in the version bundled with Ubuntu 18.10

Revision history for this message
Arttu Manninen (atmosphear) wrote :

@aamr, I solved this for Ubuntu 18.10 by disabling ibus as described here: https://askubuntu.com/questions/510430/disable-ibus-in-ubuntu-14-04

Revision history for this message
Jorge Kübler (jorge-kubler) wrote :

I can confirm this issue in the version bundled with Ubuntu 19.04

Revision history for this message
Alessandro Pocaterra (alepoc69) wrote :

Setting `Input Method Configuration` to `none` the problem is solved.

`im-config` (im-config, ver0.38-1ubuntu2, Ubuntu 19.04)
select `none`

Revision history for this message
lotuspsychje (lotuspsychje) wrote :

This still happens in Ubuntu 20.04 Beta @ 7/4/2020

Revision history for this message
Raoul Scarazzini (rasca) wrote :

Problem is still present on Ubuntu 20.04 LTS, workaround (setting "none" as input method) still fixes the issue.

Revision history for this message
Paulo Peixoto (paulogdpeixoto) wrote :

Problem still present on Ubuntu 21.04.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.