search

erase-hup / autokey

Automatically exported from code.google.com/p/autokey
GNU General Public License v3.0
0 stars 0 forks source link

Stops working/only recognises lower case #186

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. run autokey
2. use autokey and system for some time (including terminator and virtualbox)
3. after a random amount of time (sometimes straight away, sometimes after 
days) it will either
   a) auto replace, but only with lower-case versions of the upper-case activation strings
   b) stop auto completing all-together

What is the expected output? What do you see instead?
all upper-case triggers should work all of the time and should be recognised as 
upper-case

What version of the product are you using? On what operating system?
* Autokey 0.82.2
* OS: Ubuntu: 11.10
* Kernel: 3.0.0-16-generic

Please provide any additional information below.
I have always had a suspicion that wither windows under virtual box or the 
autohide terminator are at fault here, as sometimes clicking into and out of 
these apps will get autokey working again. This could just be coincidence as I 
have not been able to replicate this with any repeatability.

Original issue reported on code.google.com by chris@dirtchild.net on 8 Mar 2012 at 10:32

GoogleCodeExporter commented 9 years ago 
The only way I would be able to debug this is if you could reproduce the 
problem while running autokey with the -l command line switch for debug logging.

Original comment by cdekter on 9 Mar 2012 at 2:25

GoogleCodeExporter commented 9 years ago 
fair enough. I'll get it running now an capture the output. will note time when 
it occurs to tie back to the logs

Original comment by chris@dirtchild.net on 9 Mar 2012 at 8:18

GoogleCodeExporter commented 9 years ago 
on diggin about, I noticed errors logged and thought these might be of help? 
the "failed to ungrab" ones seem pertinent?

Original comment by chris@dirtchild.net on 14 Mar 2012 at 11:28

Attachments:

GoogleCodeExporter commented 9 years ago 
The log you attached is only the normal application log - I need the full debug 
log from running with -l in a terminal. There does seem to be a lot of strange 
X errors - I'm highly suspicious that something is wrong in your environment. 
However, let's see if the debug output provides any clues.

Original comment by cdekter on 2 Apr 2012 at 3:08

GoogleCodeExporter commented 9 years ago 
Insufficient information

Original comment by cdekter on 19 Apr 2012 at 3:45