Package Details: autokey-common 0.96.0-7

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 - common data
Upstream URL: https://github.com/autokey/autokey
Licenses: GPL-3.0-or-later
Conflicts: autokey
Provides: autokey
Submitter: dark-saber
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 69
Popularity: 0.000192
First Submitted: 2019-02-12 12:21 (UTC)
Last Updated: 2024-12-23 17:57 (UTC)

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 Next › Last »

a-bostaurus commented on 2017-09-22 08:17 (UTC) (edited on 2017-09-22 08:22 (UTC) by a-bostaurus)

autokey does not work after the last update of Manjaro stable Kernel 4.13) with Mate and XFCE. The abbreviations are not changed into the extended epressions. I cannot see any reason for this behaviour. I tried kernel 4.12, too. With this it works.

dark-saber commented on 2017-02-23 06:49 (UTC)

Fixed, thanks!

elbowz commented on 2017-02-22 13:07 (UTC)

I get this error: Autokey needs setuptools in order to build. Install it with your packagemanager (python-setuptools) or via pip (pip install setuptools) adding python-setuptools to dependencies solve the issue

dark-saber commented on 2017-01-14 15:20 (UTC)

The recent problems were introduced by this commit: https://github.com/autokey-py3/autokey/commit/2250d90d31aec0fac029ea2f9c2f1c71cfd09daf and in fact they consist of two parts: 1. 'python3-xlib' in Ubuntu is 'python-xlib' in Arch, this patches easily. 2. 'dbus-python' is somehow not found in Arch, even if python-dbus and python-dbus-common are installed. Other aliases, like 'dbus', 'python-dbus' etc. don't work too. I just patched this dep out of setup.py, especially since we still control dependencies by our distribution tools. But I still wonder what's wrong with python-dbus, some people had the same problem with blockify (https://aur.archlinux.org/packages/blockify/?comments=all), but that was resolved when this dep was removed from upstream. pip install would work, of course, but using that we're mixing Arch and python's package managers, and get all kinds of problems on further updates/removes. It would be wiser to just install autokey via pip if we're going this way.

Hal5000 commented on 2017-01-13 09:34 (UTC)

I was able to fix this problem by installing python3-xlib using pip: sudo pip install python3-xlib

ronjouch commented on 2017-01-12 22:55 (UTC) (edited on 2017-01-12 23:35 (UTC) by ronjouch)

@dark-saber: version 0.93.9-1 builds successfully but fails at runtime with an exception on python3-xlib (0.93.7-1 worked fine). Sadly, your suggestion below to @snuffop didn't work for me; here is what I tried and I still get the same exception: sudo pacman -R python-xlib autokey-py3 && sudo pacman -S python-xlib && yaourt -S autokey-py3 -------- Traceback (most recent call last): File "/usr/bin/autokey-gtk", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3019, in <module> @_call_aside File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3003, in _call_aside f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3032, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 655, in _build_master ws.require(__requires__) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 963, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 849, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'python3-xlib' distribution was not found and is required by autokey -------- ... even though python-xlib is installed: ~ sudo pacman -Syu python-xlib :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date warning: python-xlib-0.18-2 is up to date -- reinstalling :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... Packages (1) python-xlib-0.18-2 Total Installed Size: 0.76 MiB Net Upgrade Size: 0.00 MiB :: Proceed with installation? [Y/n] y (1/1) checking keys in keyring [##############################] 100% (1/1) checking package integrity [##############################] 100% (1/1) loading package files [##############################] 100% (1/1) checking for file conflicts [##############################] 100% (1/1) checking available disk space [##############################] 100% :: Processing package changes... (1/1) reinstalling python-xlib [##############################] 100%

snuffop commented on 2017-01-12 17:46 (UTC) (edited on 2017-01-12 17:47 (UTC) by snuffop)

I've re installed all pkgs built against 3.5 as well as xlib and autokey-py3 same error and trace.  pacman -Qo /usr/lib/python3.5 error: No package owns /usr/lib/python3.5

dark-saber commented on 2017-01-12 15:30 (UTC)

troxor: Thank you for maintaining the upstream! Yes, this package now defaults to GTK frontend, all GTK optdepends became mandatory. Qt optdepends will still be included in PKGBUILD for some time while mentioning their deprecated status in case someone will be able to use this frontend, however, I cannot run it anymore even with kdebindings-python-git (I guess, after the recent update to python 3.6). snuffop: python-* means python3-* in Arch. I've had similar problems with different python packages after recent python 3.6 upgrade. Here (https://aur.archlinux.org/packages/caffeine-ng/?comments=all) it is suggested to remove, then reinstall the conflicting package, and then rebuild autokey-py3. Something like this: sudo pacman -R python-xlib autokey-py3 && sudo pacman -S python-xlib && pacaur (or yaourt, or whatever) -S autokey-py3 could probably work.

snuffop commented on 2017-01-12 14:15 (UTC)

Today after Update I'm getting this trace on startup raceback (most recent call last): File "/usr/bin/autokey-gtk", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3019, in <module> @_call_aside File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3003, in _call_aside f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3032, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 655, in _build_master ws.require(__requires__) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 963, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 849, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'python3-xlib' distribution was not found and is required by autokey python-xlib and python2-xlib are installed I'm not catching the reference to python3-xlib? What am I missing?

troxor commented on 2017-01-05 17:51 (UTC)

I've picked up the torch of trying to maintain autokey-py3 upstream at https://github.com/autokey-py3/autokey. When trying to reproduce a bug, I encountered the missing kdebindings-python issue on Arch. In the meantime, a couple suggestions here: - Update the links to tarball (github release tarball) and - patch out the KDE/Qt Frontend and use just the GTK frontend in the meantime Thanks to dark-saber for maintaining this PKGBUILD!