Package Base Details: autokey

Git Clone URL: (read-only, click to copy)
Submitter: dark-saber
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 59
Popularity: 0.45
First Submitted: 2019-02-12 12:21
Last Updated: 2021-04-07 17:34

Pinned Comments

yochananmarqos commented on 2020-12-12 15:13

PSA: You may need to uninstall the old autokey package before you can upgrade to autokey-common + autokey-gtk / autokey-qt due to conflicting files.

Latest Comments

« First ‹ Previous ... 5 6 7 8 9 10 11 Next › Last »

cryzed commented on 2016-08-08 20:54

The update to python-xlib 0.16-1 seems to have broken phrase insertion for me. It seems like the entered abbreviation isn't properly recognized anymore. When manually starting autokey-qt from the console, the following traceback is shown: Here is the issue on GitHub:

EDIT: This seems to have happened because the python-xlib package in the official repositories has been updated to 0.16, which is a new release compatible with Python 3, without LiuLang's patches:

cryzed commented on 2016-06-18 12:27

This is great, thank you so much for maintaining it! I could be wrong, but I think the change suggested by @D_Schwartfeger fixed missing controls in the KDE GUI -- previously I had to rely solely on shortcuts and available context actions; I wasn't even aware that something was missing.

dark-saber commented on 2016-06-18 08:00

Fixed, thanks!

D_Schwartfeger commented on 2016-06-17 21:41

I don't know what other arch distributions are like but on Manjaro KDE I had to shift the 'autokey' folder from '/usr/share/kde4/apps/' to '/usr/share/apps/' to get the autokey-qt main window to show all the editing and config options.

Without doing this it complained of not being able to find 'autokeyui.rc' which is in this folder.

Does this need and extra post install step added to the package for arch in general? Hopefully it may help others to get it working anyway.

dark-saber commented on 2016-05-22 06:27

Fixed, thank you!

MagicAndWires commented on 2016-05-20 22:54

python-pip is not needed as a dependency; it's used for installing python packages, which in this case can be all installed through the Arch repositories or AUR.

ectospasm commented on 2016-04-23 12:47

This package fails for me if I install it through AUR. It was working, I don't know what changed (some Python library, probably python-xlib). Now when I run it with autokey-gtk --verbose, I see it gets stuck in the main X loop, with a bunch of messages regarding Xlib.error.BadAtom:

2016-04-23 07:25:07,537 ERROR - interface - Error in X event loop thread
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/autokey/", line 116, in __eventLoop
File "/usr/lib/python3.5/site-packages/autokey/", line 329, in __grabHotkeysForWindow
title = self.get_window_title(window)
File "/usr/lib/python3.5/site-packages/autokey/", line 947, in get_window_title
return self.__getWinTitle(windowvar, traverse)
File "/usr/lib/python3.5/site-packages/autokey/", line 961, in __getWinTitle
atom = windowvar.get_property(self.__VisibleNameAtom, 0, 0, 255)
File "/usr/lib/python3.5/site-packages/Xlib/xobject/", line 441, in get_property
long_length = length)
File "/usr/lib/python3.5/site-packages/Xlib/protocol/", line 1481, in __init__
File "/usr/lib/python3.5/site-packages/Xlib/protocol/", line 1501, in reply
raise self._error
Xlib.error.BadAtom: <class 'Xlib.error.BadAtom'>: code = 5, resource_id = 0, sequence_number = 84, major_opcode = 20, minor_opcode = 0

It repeats this for every event autokey captures. And while it traps events it should respond to, the error means it can't do anything with them. I have not had the time to track this down, and googling doesn't present me a solution.

If I install straight from the upstream git repository (which I've had to do to develop some patches to autokey-py3), everything is fine, no Xlib.error.BadAtom messages (and my autokey scripts actually work as expected).

I haven't had time to inspect the differences between the upstream version and the AUR package. I'd prefer installing the AUR package because then it's manageable with yaourt.

flyhunter commented on 2015-12-29 20:56

[Solved, see edit] I can't start this application. I have all the dependencies (including the optional ones) and I'm getting this error: “Error starting interface. Keyboard monitoring will be disabled. Check your system/configuration.”. The detailed error reads “~/.Xauthority: [Errno 2] No such file or directory: '/home/user/.Xauthority'”. I've added “export XAUTHORITY=/home/user/.Xauthority” to /etc/profile and the error remains. I'm running XFCE4 DE. Can anyone help me, please? Edit: "touch ~/.Xauthority" did the trick.

dark-saber commented on 2015-11-24 16:29

Updated, thank you!

DaveB commented on 2015-11-23 20:21

Hey, you might want to add an autokey-py3.install that would look something like this:

post_install() {
gtk-update-icon-cache -q -t -f /usr/share/icons/hicolor

post_remove() {

and adding:
in the declarations in your PKGBUILD.

That would take care of the icon not showing up after an install.