Package Details: autokey-gtk 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 - GTK 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.016243
First Submitted: 2019-02-12 12:21 (UTC)
Last Updated: 2024-05-14 22:14 (UTC)

Latest Comments

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

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!

nfs commented on 2016-12-30 03:40 (UTC)

After thinking about it a while, I reckon I'll wait till this is resolved upstream and there is something newer than now-deprecated pykde4. Are you going to report it upstream? Frankly, I'm not sure precisely what to report to whom. . .

dark-saber commented on 2016-12-26 19:13 (UTC)

Have you seen this topic: https://bbs.archlinux.org/viewtopic.php?id=203480? More specifically, could you check the output of these commands: $ which python $ python -c "import gi; print(gi.__spec__)" to make sure that the path to the module is /usr/lib/python3.5/site-packages/gi?

ant commented on 2016-12-26 16:48 (UTC)

Does not run. Installing python-gobject or python-gobject2 did not help: $ autokey-gtk installed with “pip install -e” Traceback (most recent call last): File "/usr/bin/autokey-gtk", line 28, in <module> from autokey.gtkapp import Application File "/usr/lib/python3.5/site-packages/autokey/gtkapp.py", line 24, in <module> from gi.repository import Gtk, Gdk, GObject, GLib ImportError: No module named 'gi.repository' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/autokey-gtk", line 31, in <module> from src.lib.gtkapp import Application ImportError: No module named 'src'

nfs commented on 2016-12-24 18:29 (UTC) (edited on 2016-12-30 03:40 (UTC) by nfs)

Thanks for clarifying. . .

dark-saber commented on 2016-12-24 14:09 (UTC)

The problem here, as far as I can see, is that KDE is dropping Qt4 support (https://wiki.debian.org/Qt4WebKitRemoval), unfortunately, including pykde4, on which autokey-qt is based. So the temporary solution is installing kdebindings-python-common and kdebindings-python from Arch Linux Archive (https://archive.archlinux.org/packages/k/kdebindings-python-common/kdebindings-python-common-4.14.3-7-x86_64.pkg.tar.xz, https://archive.archlinux.org/packages/k/kdebindings-python/kdebindings-python-4.14.3-7-x86_64.pkg.tar.xz) - for now it works. But I guess this should be reported upstream, and the upstream should eventually move on to something newer than now-deprecated pykde4.

nfs commented on 2016-12-23 17:44 (UTC)

Could you give us an indication as to when you might be able to find the time to resolve this? I'm not trying to rush you. I understand this is a busy time of the year for many of us, and it may take you a while to get around to it. I'm just wondering how often to check back here.