Comment 4 for bug 1075429

Description of problem:
If autokey phrase is set to use paste using clipboard, it will hang. If the same phrase is attempted a second time, it seems that the input device becomes non-responsive and can only be resolved by switching to a virtual terminal (outside of GNOME) to kill the misbehaving autokey-gtk process.

Version-Release number of selected component (if applicable):
Name : autokey-gtk
Arch : noarch
Version : 0.90.4
Release : 4.fc20
Size : 438 k
Repo : installed
From repo : fedora

How reproducible:
Always

Steps to Reproduce:
1. Create a autokey phrase that uses Paste using Clipboard (Ctrl+V)
2. Type the phrase's abbreviation

Actual results:
Abbreviation is erased by no output appears.

Expected results:
Abbreviation is erased and phrase appears.

Additional info:
If multiple attempts are performed, the keyboard stops responding to key input and you are left with no keyboard input device. To resolve this, you must switch to a virtual terminal (Ctrl+Alt+F2) and perform a killall autokey-gtk as the user who started the autokey process.

This was also reported for Ubuntu in Launchpad - https://bugs.launchpad.net/ubuntu/+source/autokey/+bug/1075429

The root cause of this issue is identified by the following stack:

2014-04-21 11:47:09,832 DEBUG - interface - Sending string: u'some text that should be pasted\n'
ERROR:interface:Error in X event loop thread
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/autokey/interface.py", line 116, in __eventLoop
    method(*args)
  File "/usr/lib/python2.7/site-packages/autokey/interface.py", line 500, in __sendStringClipboard
    self.__fillClipboard(string)
  File "/usr/lib/python2.7/site-packages/autokey/interface.py", line 537, in __fillClipboard
    self.clipBoard.set_text(string.encode("utf-8"))
TypeError: set_text() takes exactly 3 arguments (2 given)

After this issue occurred, I had to terminate autokey which resulted in the following abrt report: https://retrace.fedoraproject.org/faf/reports/415062/

It is important to note that the abrt report wasn't actually triggered by the hang but instead by killing the process because it became unresponsive.