key Repeat in relay group (teclas repetidas al retransmitir a grupo)

Bug #1426006 reported by FerminRJ
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Terminator
New
Undecided
Unassigned

Bug Description

In my laptop DELL LATITUDE E5540 Intel core i5 With Ubuntu 14.04 64 bit i have a problem when try to group relay ( retransmitir al grupo). The trouble is a key repeat When press any key of laptop keyboard, and the batch operations are not possible With This .

This mistake exist from the first ubuntu instalation in my laptop . The laptop is new , and is the first time that i have this problem using Terminator .

Any idea?

TERMINATOR:
Package: terminator
Section: misc
Installed-Size: 2049
Architecture: all
Version: 0.97-4
Provides: x-terminal-emulator

SO:
Ubuntu 14.10 x86_64

X:
Package: unity
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 6480
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Version: 7.3.1+14.10.20141016-0ubuntu1

Thanks !!!!

Tags: terminator
Revision history for this message
FerminRJ (ferminrj20) wrote :
tags: added: terminator
tags: added: key repeat
tags: removed: key repeat
Revision history for this message
Jon (jfindley) wrote :

I also have this bug.

OS: Ubuntu 14.10
Terminator versions tried: 0.90 0.91 0.93 0.97

Without broadcasting anything, it works fine.

If you group two or more windows, or broadcast to all, the main window will be OK, but all other broadcast recipients will receive two key-press-events in most cases, and sometimes an infinite loop will occurr where the same key-press-event is repeated indefinitely.

I hackily restored functionality by adding a dictionary of terminals (populated by group_emit) and the timestamp of the last time a key-press-event was emitted, then in group_emit in terminator.py I would either skip emitting for this term if the elapsed time is less than 0.01 seconds otherwise I would emit and update the last event time in the dictionary.

This only sort of works, though, as it seems that detecting which terminal is actually the selected one is flakey, too. I have to make sure I selected the first terminal created before typing, otherwise the first one won't receive any events at all.

I would quit my job, throw away all my computers, and commit myself if I no longer was able to use terminator. It is better than my morning coffee, or a nice date with my wife. It is the reason I wake up in the morning. Please help me!

Revision history for this message
trick7 (trick7) wrote :

I have a similar behavior:
With 2 or 3 splitted terminator, I get 2 chars per input in all grouped windows.

When I use 4 splitted windows, the CPU utilisation raises to 100% with no output.
When I click the terminator programm close button, I'm asked for closing terminator.
Then I can see the keyloop in all grouped windows. But the window where I typed in gets no char.

Revision history for this message
trick7 (trick7) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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