Autokey stops working after a couple of hours or more
Johnny Rosenberg
you guys here seems to know stuff about not only Autokey…
So if I leave my laptop on over the night it's likely that my Autokey
phrases (and possible the few scripts I have that I almost never use,
but I didn't try them, but I will next time…) doesn't work after that.
I have two laptops and this happens for both of them, and I am sure
this has nothing to do with my own keyboard layout since it's have
never even been near one of my laptops.
Autokey itself works. I can open its main window and add phrases and
so on, but my abbreviations doesn't work.
The reason why I think that it's not Autokeys fault, is that closing
and restarting Autokey doesn't help. Loggin out from Ubuntu and
logging in again also doesn't help. Restarting my computer always
helps, of course.
So why am I writing here? Well, I don't know anywhere else to write…
What would happen if I wrote to some Ubuntu list? Well, they would
probably advice me not to use Autokey, and we don't want that, do we…?
So I was just wondering if anyone here could tell me some hints on how
to figure out what goes wrong here. It seems like something in my
system crash eventually, maybe Autokey causes it, maybe not. But I am
a guitarist, not a computer ”expert” (neither am I a beginner, though)
so I just need a little help here, I think.
Thanks
Regards
Johnny Rosenberg
Chris Dekter
Visuex
Just to clarify, it only happens when you leave your computer on
overnight and not if you say turn it on in the morning and then try
again at night like for example 12 hours later. Is that correct?
If so, I wonder are you putting your machine to sleep or in
hibernation mode during the night or are you just leaving it running
like normal?
Johnny Rosenberg
> Which version of Ubuntu, and which interface within AutoKey are you using?
Ooops, sorry. Just assumed that everyone always use the latest updates.
Here are ny info:
Packard Bell EasyNote MX-66 204D – 1,6 GHz T2050, 2 GiB
Kernel: Linux 2.6.32-24-generic
Gnome 2.30.2
Ubuntu 10.04
AutoKey GTK 0.71.0
Eee PC 900 – 900 MHz Intel Celeron M processor, 993,7 MiB
Kernel: Linux 2.6.32-24-generic
Gnome 2.30.2
Ubuntu 10.04 (NOT the ”netbook remix” version)
AutoKey GTK 0.70.4
Regards
Johnny Rosenberg
Chris Dekter
Johnny Rosenberg
> Johnny,
> Just to clarify, it only happens when you leave your computer on
> overnight and not if you say turn it on in the morning and then try
> again at night like for example 12 hours later. Is that correct?
Right. However I am not sure if it happens only if I don't do anything
for a couple of hours or if it would happen if I constantly work with
it for that time. I guess that could be figured out too, but it
doesn't happen very often that I sit here for so many hours in a row…
What I've seen so far, is that when my computer has been on for a long
time, my AutoKey abbreviations don't work anymore and it doesn't help
to restart AutoKey. That's why I think that something crashed in my
system. I guess this would be documented in one of the many log files,
but it's hard to know where to start looking… They are in /var
somewhere, aren't they?
>
> If so, I wonder are you putting your machine to sleep or in
> hibernation mode during the night or are you just leaving it running
> like normal?
Leaving it running. For example last time it happened, this morning, I
ran a backup script (a bash script that I made myself – nothing fancy,
it just runs rsync with some common parameters) and since I expected
it to take quite some time I left it on and went to bed.
Regards
Johnny Rosenberg
Johnny Rosenberg
> When I said which interface, I meant as in Record/Evdev/etc...
He he he… ok, misunderstanding there. Evdev on both machines,
Derek
Derek
Johnny Rosenberg said the following on 08/10/2010 11:52 PM:
Johnny Rosenberg
> I wonder if this is related to Issue 43. I haven't found any more insight
> into it, but since I leave my computer on at night, I quit AutoKey each
> evening. Otherwise, it consumes a lot of memory and the computer is bogged
> down the next day. This is on Ubuntu 10.04 with recent versions of AutoKey
> with the X Record interface. I don't know how far back it goes, though I
> never experienced the problem on Hardy.
>
> Derek
I'm not sure it's the same, but maybe related somehow. By the way, I
have had my computer running for a couple of hours now and AutoKey
still works, and last time I checked, a minute or two ago, it consumed
14,5 MiB.
Regards
Johnny Rosenberg
Johnny Rosenberg
Okay, now when I came back after being out for some hours running and
doing some more stuff, abbreviations didn't work any more. The same
thing happened a few days ago and this is what I did back then after
that:
First I quit AutoKey, then I ran autokey-gtk -l.
Typing elsewhere and clicking with the mouse didn't lead to any kind
of activity in the terminal, it seemed like autokey-gtk didn't receive
any information from the system, or however it works. Suddenly when I
clicked somewhere things stareed to happen in the terminal again and
everything worked perfectly after a while. At first it was a bit slow
with long delays between typing and replacing my abbreviations with
phrases, but efter a while it work perfectly.
Today, however, I did the same thing but I can't really get it to work
this time. First I quit AutoKey, then started autokey-gtk -l from a
terminal again, just like the other day. The following fills the
screen (just like the other day):
$ autokey-gtk -l
INFO - root - Initialising application
INFO - config-manager - Loading config from existing file:
/home/guraknugen/.config/autokey/autokey.json
INFO - config-manager - Configuration changed - rebuilding in-memory structures
INFO - config-manager - Persisting configuration
INFO - config-manager - Backing up existing config file
INFO - config-manager - Finished persisting configuration - no errors
INFO - root - Initialise global hotkeys
INFO - config-manager - Successfully loaded configuration file
DEBUG - config-manager - Global settings: {'showTrayIcon': True,
'windowDefaultSize': [1020, 522], 'undoUsingBackspace': False,
'enableQT4Workaround': False, 'promptToSave': False, 'interfaceType':
u'XEvDev', 'showToolbar': True, 'serviceRunning': True,
'columnWidths': [150, 50, 100], 'isFirstRun': False,
'sortByUsageCount': True, 'notificationIcon':
u'/usr/share/pixmaps/akicon.png', u'inputSavings': 7883,
'hPanePosition': 563, 'menuTakesFocus': False}
INFO - service - Starting service
Xlib.protocol.request.QueryExtension
DEBUG - interface - Modifier masks: {'<alt_gr>': 128, '<numlock>': 16,
'<ctrl>': 4, '<shift>': 1, '<alt>': 8, '<super>': 64}
DEBUG - interface - Grabbing hotkey: [u'<ctrl>'] u'k'
DEBUG - interface - Grabbing hotkey: [u'<ctrl>', u'<shift>'] u'k'
DEBUG - interface - Grabbing hotkey: [u'<alt>', u'<ctrl>', u'<shift>'] u'y'
DEBUG - interface - Grabbing hotkey: [u'<alt>', u'<ctrl>', u'<shift>'] u'm'
DEBUG - interface - Alt-Grid: XK_ISO_Level3_Shift, 65027
DEBUG - interface - [(92, 0), (108, 0), (92, 2), (108, 2)]
DEBUG - interface - X Server Keymap
DEBUG - interface - [\] : [(20, 4)]
DEBUG - interface - [|] : [(94, 4)]
DEBUG - interface - No mapping for [`]
DEBUG - interface - [1] : [(10, 0), (10, 2)]
DEBUG - interface - [2] : [(11, 0), (11, 2)]
DEBUG - interface - [3] : [(12, 0), (12, 2)]
DEBUG - interface - [4] : [(13, 0), (13, 2)]
DEBUG - interface - [5] : [(14, 0), (14, 2)]
DEBUG - interface - [6] : [(15, 0), (15, 2)]
DEBUG - interface - [7] : [(16, 0), (16, 2)]
DEBUG - interface - [8] : [(17, 0), (17, 2)]
DEBUG - interface - [9] : [(18, 0), (18, 2)]
DEBUG - interface - [0] : [(19, 0), (19, 2)]
DEBUG - interface - [-] : [(61, 0), (61, 2)]
DEBUG - interface - [=] : [(19, 1), (19, 3)]
DEBUG - interface - No mapping for [~]
DEBUG - interface - [!] : [(10, 1), (10, 3)]
DEBUG - interface - [@] : [(11, 4), (24, 4)]
DEBUG - interface - [#] : [(12, 1), (12, 3)]
DEBUG - interface - [$] : [(13, 4)]
DEBUG - interface - [%] : [(14, 1), (14, 3)]
DEBUG - interface - No mapping for [^]
DEBUG - interface - [&] : [(15, 1), (15, 3), (45, 5)]
DEBUG - interface - [*] : [(51, 1), (51, 3)]
DEBUG - interface - [(] : [(187, 0), (17, 1), (187, 2), (17, 3)]
DEBUG - interface - [)] : [(188, 0), (18, 1), (188, 2), (18, 3)]
DEBUG - interface - [q] : [(24, 0), (24, 2)]
DEBUG - interface - [w] : [(25, 0), (25, 2)]
DEBUG - interface - [e] : [(26, 0), (26, 2)]
DEBUG - interface - [r] : [(27, 0), (27, 2)]
DEBUG - interface - [t] : [(28, 0), (28, 2)]
DEBUG - interface - [y] : [(29, 0), (29, 2)]
DEBUG - interface - [u] : [(30, 0), (30, 2)]
DEBUG - interface - [i] : [(31, 0), (31, 2)]
DEBUG - interface - [o] : [(32, 0), (32, 2)]
DEBUG - interface - [p] : [(33, 0), (33, 2)]
DEBUG - interface - [[] : [(17, 4)]
DEBUG - interface - []] : [(18, 4)]
DEBUG - interface - [a] : [(38, 0), (38, 2)]
DEBUG - interface - [s] : [(39, 0), (39, 2)]
DEBUG - interface - [d] : [(40, 0), (40, 2)]
DEBUG - interface - [f] : [(41, 0), (41, 2)]
DEBUG - interface - [g] : [(42, 0), (42, 2)]
DEBUG - interface - [h] : [(43, 0), (43, 2)]
DEBUG - interface - [j] : [(44, 0), (44, 2), (44, 4)]
DEBUG - interface - [k] : [(45, 0), (45, 2)]
DEBUG - interface - [l] : [(46, 0), (46, 2)]
DEBUG - interface - [;] : [(59, 1), (59, 3)]
DEBUG - interface - ['] : [(51, 0), (51, 2)]
DEBUG - interface - [z] : [(52, 0), (52, 2)]
DEBUG - interface - [x] : [(53, 0), (53, 2)]
DEBUG - interface - [c] : [(54, 0), (54, 2)]
DEBUG - interface - [v] : [(55, 0), (55, 2)]
DEBUG - interface - [b] : [(56, 0), (56, 2)]
DEBUG - interface - [n] : [(57, 0), (57, 2), (57, 4)]
DEBUG - interface - [m] : [(58, 0), (58, 2)]
DEBUG - interface - [,] : [(59, 0), (59, 2)]
DEBUG - interface - [.] : [(60, 0), (60, 2)]
DEBUG - interface - [/] : [(16, 1), (16, 3)]
DEBUG - interface - [Q] : [(24, 1), (24, 3)]
DEBUG - interface - [W] : [(25, 1), (25, 3)]
DEBUG - interface - [E] : [(26, 1), (26, 3)]
DEBUG - interface - [R] : [(27, 1), (27, 3)]
DEBUG - interface - [T] : [(28, 1), (28, 3)]
DEBUG - interface - [Y] : [(29, 1), (29, 3)]
DEBUG - interface - [U] : [(30, 1), (30, 3)]
DEBUG - interface - [I] : [(31, 1), (31, 3)]
DEBUG - interface - [O] : [(32, 1), (32, 3)]
DEBUG - interface - [P] : [(33, 1), (33, 3)]
DEBUG - interface - [{] : [(16, 4)]
DEBUG - interface - [}] : [(19, 4)]
DEBUG - interface - [A] : [(38, 1), (38, 3)]
DEBUG - interface - [S] : [(39, 1), (39, 3)]
DEBUG - interface - [D] : [(40, 1), (40, 3)]
DEBUG - interface - [F] : [(41, 1), (41, 3)]
DEBUG - interface - [G] : [(42, 1), (42, 3)]
DEBUG - interface - [H] : [(43, 1), (43, 3)]
DEBUG - interface - [J] : [(44, 1), (44, 3), (44, 5)]
DEBUG - interface - [K] : [(45, 1), (45, 3)]
DEBUG - interface - [L] : [(46, 1), (46, 3)]
DEBUG - interface - [:] : [(60, 1), (60, 3)]
DEBUG - interface - ["] : [(11, 1), (11, 3)]
DEBUG - interface - [Z] : [(52, 1), (52, 3)]
DEBUG - interface - [X] : [(53, 1), (53, 3)]
DEBUG - interface - [C] : [(54, 1), (54, 3)]
DEBUG - interface - [V] : [(55, 1), (55, 3)]
DEBUG - interface - [B] : [(56, 1), (56, 3)]
DEBUG - interface - [N] : [(57, 1), (57, 3), (57, 5)]
DEBUG - interface - [M] : [(58, 1), (58, 3)]
DEBUG - interface - [<] : [(94, 0), (94, 2), (52, 5)]
DEBUG - interface - [>] : [(94, 1), (94, 3), (53, 5)]
DEBUG - interface - [?] : [(20, 1), (20, 3)]
DEBUG - iomediator - Set modifier <capslock> to False
DEBUG - iomediator - Set modifier <numlock> to True
INFO - interface - Attempting to establish connection to EvDev daemon
INFO - interface - EvDev daemon connected
INFO - interface - EvDev interface thread starting
INFO - service - Service now marked as running
INFO - root - Entering main()
After this, nothing more happens in the terminal.
I quit and restarted AutoKey a couple of more times but no success,
but after a few times I get the following error message every time I
start AutoKey:
Error starting Interface. Keyboard monitoring will be disabled.
Check your system/configuration.
Unable to connect to EvDev daemon:
[Errno 11] Resursen tillfälligt otillgänglig
The last line is in Swedish, it means something like ”The resource is
temporarily unavailable”.
I guess restarting my computer is the only way I can get it up running
at the moment so that is what I'm going to do.
And as usual, this is my computer info:
AutoKey-gtk 0.71.0
Ubuntu 10.04
Keyboard layout: The Swedish default layout (my own layout is
completely removed from the system since long ago, so don't worry
about that. I miss it very much so I will bring it back as soon as
possible, but not before this problem is solved or at least addressed,
I think…).
J.R.
Johnny Rosenberg
Here's the terminal output when the EvDev error above occurs:
$ autokey-gtk -l
INFO - root - Initialising application
INFO - config-manager - Loading config from existing file:
/home/guraknugen/.config/autokey/autokey.json
INFO - config-manager - Configuration changed - rebuilding in-memory structures
INFO - config-manager - Persisting configuration
INFO - config-manager - Backing up existing config file
INFO - config-manager - Finished persisting configuration - no errors
INFO - root - Initialise global hotkeys
INFO - config-manager - Successfully loaded configuration file
DEBUG - config-manager - Global settings: {'showTrayIcon': True,
'windowDefaultSize': [1020, 522], 'undoUsingBackspace': False,
'enableQT4Workaround': False, 'promptToSave': False, 'interfaceType':
u'XEvDev', 'showToolbar': True, 'serviceRunning': False,
ERROR - root - Error starting interface: Unable to connect to EvDev daemon:
[Errno 11] Resursen tillfälligt otillgänglig
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/autokey/gtkapp.py", line 125,
in initialise
self.service.start()
File "/usr/lib/python2.6/dist-packages/autokey/service.py", line 77, in start
self.mediator = IoMediator(self)
File "/usr/lib/python2.6/dist-packages/autokey/iomediator.py", line
142, in __init__
self.interface = EvDevInterface(self, service.app)
File "/usr/lib/python2.6/dist-packages/autokey/interface.py", line
708, in __init__
self.__connect()
File "/usr/lib/python2.6/dist-packages/autokey/interface.py", line
765, in __connect
raise Exception("Unable to connect to EvDev daemon:\n" + str(e))
Exception: Unable to connect to EvDev daemon:
[Errno 11] Resursen tillfälligt otillgänglig
INFO - root - Entering main()
J.R.
Johnny Rosenberg
Looks like my system installed a kernel update while I was out,
because when I was going to restart my laptop the text ”Restart” was
replaced by ”Restart required” or something like that (”Omstart krävs”
in Swedish…). Maybe this was the reason this time why AutoKey stopped
working. Maybe some parts of the system was just shut down for some
reason that is connected to the update.
So maybe it was a false alarm this time, but still, this happens now
and then. On both of my computers, which are configured a lot
different from each other. The other one only has the most important
software installed, because its SSD drive is very small (16 GiB).
Regards
Johnny Rosenberg
Johnny Rosenberg
This still happens now and then on both my computers. Actually it
happened right now.
After a while my phrases doesn't work at all. Restarting Autokey does
not help. I also tried the other two interfaces, no luck at all.
I also tried to start AutoKey from a terminal with the -l option and
got the following output:
$ autokey-gtk -l
INFO - root - Initialising application
INFO - config-manager - Loading config from existing file:
/home/guraknugen/.config/autokey/autokey.json
INFO - config-manager - Configuration changed - rebuilding in-memory structures
INFO - config-manager - Persisting configuration
INFO - config-manager - Backing up existing config file
INFO - config-manager - Finished persisting configuration - no errors
INFO - root - Initialise global hotkeys
INFO - config-manager - Successfully loaded configuration file
DEBUG - config-manager - Global settings: {'showTrayIcon': True,
'windowDefaultSize': [956, 517], 'undoUsingBackspace': False,
'enableQT4Workaround': False, 'promptToSave': False, 'interfaceType':
u'AT-SPI', 'showToolbar': True, 'serviceRunning': True,
'columnWidths': [150, 50, 100], 'isFirstRun': False,
'sortByUsageCount': True, 'notificationIcon':
u'/usr/share/pixmaps/akicon.png', u'inputSavings': 7883,
'hPanePosition': 528, 'menuTakesFocus': False}
INFO - service - Starting service
Xlib.protocol.request.QueryExtension
DEBUG - interface - Modifier masks: {'<alt_gr>': 128, '<numlock>': 16,
'<ctrl>': 4, '<shift>': 1, '<alt>': 8, '<super>': 64}
DEBUG - interface - Grabbing hotkey: [u'<ctrl>'] u'k'
DEBUG - interface - Grabbing hotkey: [u'<ctrl>', u'<shift>'] u'k'
DEBUG - interface - Grabbing hotkey: [u'<alt>', u'<ctrl>', u'<shift>'] u'y'
DEBUG - interface - Grabbing hotkey: [u'<alt>', u'<ctrl>', u'<shift>'] u'm'
ERROR - root - Error starting interface: get_window_title() takes
exactly 1 argument (2 given)
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/autokey/gtkapp.py", line 124,
in initialise
self.service.start()
File "/usr/lib/python2.6/dist-packages/autokey/service.py", line 76, in start
self.mediator = IoMediator(self)
File "/usr/lib/python2.6/dist-packages/autokey/iomediator.py", line
143, in __init__
self.interface = AtSpiInterface(self, service.app)
File "/usr/lib/python2.6/dist-packages/autokey/interface.py", line
82, in __init__
self.__initMappings()
File "/usr/lib/python2.6/dist-packages/autokey/interface.py", line
121, in __initMappings
self.__grabHotkeys()
File "/usr/lib/python2.6/dist-packages/autokey/interface.py", line
160, in __grabHotkeys
self.__recurseTree(self.rootWindow, hotkeys)
File "/usr/lib/python2.6/dist-packages/autokey/interface.py", line
165, in __recurseTree
title = self.get_window_title(window)
TypeError: get_window_title() takes exactly 1 argument (2 given)
INFO - root - Entering main()
I have done this before when Autokey stopped working, but this is the
first time I get that error at the end…
Kind regards
Johnny Rosenberg
ジョニー・ローゼンバーグ
John Niendorf
Johnny Rosenberg
> I had / have the same issue with Ubuntu 10.10 and 11.04. The only way I
> figured to solve the problem is to have a cron job set to kill autokey once
> an hour then another job to restart it a couple of minutes later.
> John
>
If you start Autokey manually, does it work then? For me it usually
doesn't but sometimes (very few times) it does.
Johnny Rosenberg
Just found out that this error only happens with the AT-SPI interface.
Johnny Rosenberg
Maybe that message was very confusing… This is what I mean:
Autokey stopped working → I cancelled Autokey → I started Autokey →
Still no luck → I changed to the X record interface → Still no luck →
Changed to the AT-SPI interface → Still no luck → I cancelled Autokey
→ I started Autokey → Error message at Autokey startup → I tried to
restart several times, same error → Restarted my computer → Same error
→ A couple of more restarts → Same error → I cancelled Autokey → I
started Autokey → I changed to another interface, X record I think →
No error → Changed to the X Evdev interface → Still no error
Right now Autokey works since I restarted my computer recently, so I
can't do any further tests at the moment…
Evan Edwards
> I had / have the same issue with Ubuntu 10.10 and 11.04. The only way I
> figured to solve the problem is to have a cron job set to kill autokey once
> an hour then another job to restart it a couple of minutes later.
I find once a day is typically enough. There is an odd issue, however.
---- code start ----
#!/bin/sh
#%%about=ak - Restart AutoKey
if [ ! "$1" = "" ]
then
echo "Usage: ak"
echo " Restarts Autokey"
exit
fi
killall autokey-qt
sleep .3
killall -9 autokey-qt 2>/dev/null
sleep .2
autokey-qt >/dev/null 2>&1 &
---- code end ----
--
Evan Edwards
ev...@cheshirehall.net
814.889.8845
Johnny Rosenberg
back AutoKey-GTK didn’t work. This time I didn’t restart my computer
(which was the only way that I knew of before), instead I did the
following:
1. Change interface to X Record.
2. Try again – no success.
3. Cancel AutoKey-GTK.
4. Start AutoKey-GTK.
5. Try again – success.
6. Change interface back to X Evdev.
5. Try again – success.
Does this give you guys any kinds of clues on what’s going on? It
doesn’t seem to be something in my system that crashed, because the
only thing I restarted was AutoKey-GTK. Can it be a bug in Python? I
guess I wouldn't have asked that if I knew anything about Python,
though…
So the possible steps here seems to be the following:
1–2–3–4–5–6–5.
1–2–3–4–5 (if you don’t mind X Record instead of X Evdev).
3–4–2 (which means that if you only do step 3 and 4, you will end up
at step 2 rather than step 5).
I didn’t try 3–4–1 or 3–4–1–6 though.
Regards
Johnny Rosenberg
ジョニー・ローゼンバーグ
Joe
inactive recently. I don't remember exactly what steps I took to get it
to start working again, but it was more that just closing it and running
it again. This is just to say that more than one person is having this
problem.
Joe
Chris D
doesn't work at all. Try using that exclusively and see if it
eliminates this problem.
Johnny Rosenberg
> The best choice for interface type is always XRecord unless that
> doesn't work at all. Try using that exclusively and see if it
> eliminates this problem.
Have done that since last time I wrote, I think, and as far as I
remember I had no problems so far. If it happens again, I will write
back.
Still, I am curious why it fails sometimes when using the X evdev
interface. Where is the problem? AutoKey, Python, Evdev? I guess
nobody knows at the moment, but if someone finds out I'd like to know.
Kind regards
Johnny Rosenberg
ジョニー・ローゼンバーグ
>