Package Details: autokey-qt 0.96.0-6

Git Clone URL: https://aur.archlinux.org/autokey.git (read-only, click to copy)
Package Base: autokey
Description: A desktop automation utility for Linux and X11 - Qt frontend
Upstream URL: https://github.com/autokey/autokey
Licenses: GPL-3.0-or-later
Submitter: dark-saber
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 69
Popularity: 0.000326
First Submitted: 2019-02-12 12:21 (UTC)
Last Updated: 2024-05-14 22:14 (UTC)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14

ectospasm commented on 2016-04-23 12:47 (UTC)

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/interface.py", line 116, in __eventLoop method(*args) File "/usr/lib/python3.5/site-packages/autokey/interface.py", line 329, in __grabHotkeysForWindow title = self.get_window_title(window) File "/usr/lib/python3.5/site-packages/autokey/interface.py", line 947, in get_window_title return self.__getWinTitle(windowvar, traverse) File "/usr/lib/python3.5/site-packages/autokey/interface.py", line 961, in __getWinTitle atom = windowvar.get_property(self.__VisibleNameAtom, 0, 0, 255) File "/usr/lib/python3.5/site-packages/Xlib/xobject/drawable.py", line 441, in get_property long_length = length) File "/usr/lib/python3.5/site-packages/Xlib/protocol/rq.py", line 1481, in __init__ self.reply() File "/usr/lib/python3.5/site-packages/Xlib/protocol/rq.py", 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 (UTC) (edited on 2016-01-03 21:05 (UTC) by flyhunter)

[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 (UTC)

Updated, thank you!

DaveB commented on 2015-11-23 20:21 (UTC)

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() { post_install } and adding: install=${pkgname}.install in the declarations in your PKGBUILD. That would take care of the icon not showing up after an install.

nhasian commented on 2015-07-29 23:12 (UTC)

after manually installing a few of the missing dependencies (python-pip and python-xlib) this Python3 port of autokey works great! unlike autokey-gtk which currently is not functioning unfortunately.

« First ‹ Previous 1 .. 9 10 11 12 13 14