Autokey-gtk broken in Opera on new Fedora 20/64 install.
GoogleCodeExporter opened this issue · comments
What steps will reproduce the problem?
1. On Fedora 20, start autokey-gtk, then open the Opera 12.16 browser.
2. Visit a MediaWiki site that I administer.
3. Open a new wikitext page for update. Start typing, then use autokey to
insert some existing template.
What is the expected output? What do you see instead?
Typing worked OK until feeding some autokey phrase.
Instead of the expected text, gibberish appears. After this, typing any key
keeps producing only gibberish, no more text input possible.
Further interactions with the MediaWiki page will all produce only gibberish,
e.g. search box.
Eventually, within the next minute, Opera will freeze.
This is repeatable 100% so far.
What version of the product are you using? On what operating system?
autokey-gtk-0.90.4-4.fc20.noarch
autokey-qt-0.90.4-4.fc20.noarch
autokey-common-0.90.4-4.fc20.noarch
All this on Fedora 20/64.
Please provide any additional information below.
The feature worked perfectly fine under Fedora 17/64 using
autokey-0.81.4-1.fc17.noarch
The current autokey installation works OK with other browsers such as Firefox,
Google Chrome.
I have a preference for Opera, but this prevents any reasonable use. My job
depends on updating MediaWiki pages, and Opera does this faster.
I posted the following in the Opera forum:
While on Fedora 17, I used opera-12.16-1860.x86_64 from the official RPM
download. It worked quite fine, making it (again) my favorite for 90%+ of my
browsing activity (best speed, nicest rendering among other virtues, good job
Opera!).
However, my most frequent use is to update a MediaWiki based site. I rely
heavily on autokey-gtk to insert chunks of text (e.g. Wikitext templates) by
using shortcut abbreviations within the MediaWiki edit form. This worked nicely
until I needed to update to Fedora 20. The Opera version hasn't changed, but
this feature is now broken.
It will start to insert gibberish as soon as I used one of my autokey
sequences, and within the next few minutes Opera will become totally
unresponsive - no crash report, it just freezes.
Tried disabling extensions, changing compatibility to Opera 9.6, no effect -
keeps freezing in that specific use. Other navigation, webmail, etc. just fine.
Only my needed autokey interaction is broken...
I tried another Wiki running with a more recent LAMP stack, with same results.
Other 2 mainstream browsers are working just fine after the transition,
receiving & expanding the autokey sequences w/o issues.
What can be going on, is there a fix in sight ? I've seen a post of a user
having a similar problem with just plain forms, but mine seems only related to
auto-key. If I don't use it, the Wiki edit windows (and other forms) work fine.
Thanks!
Original issue reported on code.google.com by davidram...@gmail.com
on 7 Apr 2014 at 4:35
Additional comments:
Running with -l produces no abnormal results: I see the keys being pressed
appear (but the debug mode seems unable to expand the phrases) - also mouse
events.
Original comment by davidram...@gmail.com
on 7 Apr 2014 at 4:37
I have the same problem under Ubuntu 14,04. It worked fine on 12.10, and on a
halfway upgrade of 13.04 or 13.10 (not sure which). Now that I'm on 14.04,
using a hotkey or an auto-expand phrase turns into gibberish and freezes
further keyboard input to Opera until I kl\ill and restart it.
Opera 12.16, autokey-gtk 0.90.4. I'm pretty sure the Opera version has not
changed. Autokey may have upgraded as part of my whole Ubuntu upgrade.
Original comment by norri...@gmail.com
on 8 Aug 2014 at 3:25
#288 #277 #288 all seem related.
Original comment by carl.hea...@gmail.com
on 20 Oct 2014 at 9:22
[deleted comment]
[deleted comment]
Small update: I have the same problems using autokey within skype or launchy as
I do within Opera.
Original comment by norri...@gmail.com
on 21 Oct 2014 at 12:47
I'm also experiencing the exact same issue, but with Opera, Chromium and
Firefox.
I'm running Kubuntu 14.10 with Autokey 0.90.4. It will work with editors but
not with any web browser. It generates gibberish and messes up the keyboard
response.
Original comment by briandwr...@gmail.com
on 18 Dec 2014 at 12:21