Search Criteria
Package Details: autokey-qt 0.96.0-2
Package Actions
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: | GPL3 |
Submitter: | dark-saber |
Maintainer: | yochananmarqos |
Last Packager: | yochananmarqos |
Votes: | 66 |
Popularity: | 0.178735 |
First Submitted: | 2019-02-12 12:21 (UTC) |
Last Updated: | 2022-06-06 18:23 (UTC) |
Dependencies (11)
- autokey-common
- kdialog (kdialog-git)
- python-pyqt5 (python-pyqt5-sip4)
- python-qscintilla-qt5
- qt5-svg (qt5-svg-git)
- python-build (make)
- python-installer (python-installer-git) (make)
- python-pyqt5 (python-pyqt5-sip4) (make)
- python-setuptools (make)
- python-wheel (make)
- qt-at-spi (optional)
Latest Comments
AvidSeeker commented on 2022-06-30 12:29 (UTC)
autokey-common could not find packages Tried installing autokey from AUR.
gives the error:
am I missing some repos in my mirror list? I tried manually installing these packages (with adding them to PATH), still not solved.
BlueDrink9 commented on 2022-06-06 00:02 (UTC)
New release! https://github.com/autokey/autokey/releases/tag/v0.96.0
ronjouch commented on 2022-04-15 16:22 (UTC)
@yochananmarqos confirmed! Thanks for the quick fix, and thanks for the package maintenance.
yochananmarqos commented on 2022-04-15 16:02 (UTC)
@ronjouch: Oops. It's fixed now.
ronjouch commented on 2022-04-15 15:23 (UTC)
Even after removing
autokey-gtk autokey-common
, installing -5 is impossible because of conflicts:mpj4 commented on 2022-02-02 07:50 (UTC)
Can't connect to display ":0.0": b'Invalid MIT-MAGIC-COOKIE-1 key'
fixed it by deleting $HOME/.Xauthority and rebooting
hicklemon commented on 2021-12-14 17:44 (UTC)
I'm on python 3.10.1 and I got it working again. I had to manually reinstall autokey-common && autokey-gtk
Archanfel80HUN commented on 2021-12-14 17:16 (UTC) (edited on 2021-12-14 17:20 (UTC) by Archanfel80HUN)
Broken with python 3.10.x (works with 3.9.x):
Traceback (most recent call last): File "/usr/bin/autokey-gtk", line 33, in <module> sys.exit(load_entry_point('autokey==0.95.10', 'console_scripts', 'autokey-gtk')()) File "/usr/bin/autokey-gtk", line 22, in importlib_load_entry_point for entry_point in distribution(dist_name).entry_points File "/usr/lib/python3.10/importlib/metadata/init.py", line 919, in distribution return Distribution.from_name(distribution_name) File "/usr/lib/python3.10/importlib/metadata/init.py", line 518, in from_name raise PackageNotFoundError(name) importlib.metadata.PackageNotFoundError: No package metadata was found for autokey
hicklemon commented on 2021-04-12 14:26 (UTC)
Hello,
A recent update seems to have created some conflicts with autokey-common and autokey-gtk if the user has pyenv installed.
In order to get around this, I cleaned up my PATH and pyenv vars temporarily:
This seems to have worked
Ray commented on 2021-01-16 21:19 (UTC)
I just found this AUR and used it to replace old Autokey that no longer functioned. Autokey is a critical application for so many of us. I hope development will continue. Thank you for updating this package.
buzuddha commented on 2020-12-17 02:32 (UTC) (edited on 2020-12-17 02:38 (UTC) by buzuddha)
Gotcha. Was in the autokey directory. Just didn't realize I needed to add the version numbers and extension.
seemed to do it. Same worked for for autokey-gtk.
Thanks for your help!
yochananmarqos commented on 2020-12-17 02:28 (UTC)
@buzuddha: You already built the packages, now go to the
$PKGDEST
and install them. Also seeman makepkg
and read the Arch wiki page.buzuddha commented on 2020-12-17 02:23 (UTC)
Hmmm...
I get the same with
and then the pacman install. Any thoughts?yochananmarqos commented on 2020-12-17 01:55 (UTC) (edited on 2020-12-17 01:56 (UTC) by yochananmarqos)
@buzuddha: Build the package without
-i
, then install manually after:Then either:
Or:
buzuddha commented on 2020-12-17 01:39 (UTC)
I'm having an issue with updating autokey. The long story is here: https://bbs.archlinux.org/viewtopic.php?pid=1943997#p1943997
The short story is :: autokey-gtk and autokey-qt are in conflict during makepkg -si of auotkey-common. Anything I'm missing?
yochananmarqos commented on 2020-12-16 23:07 (UTC)
@zhimsel: Good catch, fixed.
zhimsel commented on 2020-12-16 22:55 (UTC)
FYI, the PKGBUILD as-is is broken (at least on my system). All the
rm
commands for the pycache files need to berm -f
. Those file don't exist (on my system), so the plainrm
command fails.https://gist.github.com/zhimsel/2c794f552d19e175f7fb8f5854cfa85e
yochananmarqos commented on 2020-12-12 15:13 (UTC)
PSA: You may need to uninstall the old
autokey
package before you can upgrade toautokey-common
+autokey-gtk
/autokey-qt
due to conflicting files.ectospasm commented on 2020-12-09 04:28 (UTC)
It looks like Arch pushed out a new version of Python (3.9). I ran into errors running
autokey-gtk
andautokey-qt
, because the Python moduleautokey
was not found. My AUR helper (pikaur
) does not rebuild AUR packages when this happens (not sure if that's just the default pikaur configuration or I have it configured not to rebuild). I had to install the PKGBUILD manually to workaround it.I probably could have fixed it by telling pikaur to rebuild the PKGBUILD, instead of running
makepkg -sri
in the directory where the PKGBUILD lives. Just a gotcha that seems to be hitting a lot of my Python programs lately.ectospasm commented on 2020-12-04 02:58 (UTC) (edited on 2020-12-09 04:24 (UTC) by ectospasm)
@F-D: What makes you think we can support you here? Either consult your non-Arch OS's forums/bug trackers (Manjaro is NOT Arch!), or seek help from upstream.
The phrase "patched as well as non-patched" has no relevance here. What have you patched? What patch(es) did you apply? Since you don't use Arch we can't help you, as we know nothing of the customization Manjaro has introduced when you installed it. Would you go to Debian to get help with Ubuntu? Would you go to Gentoo to get help with Sabayon? Would you go to Red Hat to get help with Fedora, or CentOS? The answer should be,"No." If your chosen OS's forums/bug tracker is useless or dead, pick a better Linux distribution, or go upstream to get help.
EDIT: Oh, I see. There are two AUR packages for autokey: autokey (this page), and autokey-patched. You're still barking up the wrong tree, Manjaro is NOT Arch. See https://wiki.archlinux.org/index.php/Code_of_conduct#Arch_Linux_distribution_support_ONLY in the Arch Linux Code of Conduct.
properlypurple commented on 2020-12-03 10:16 (UTC)
I just copied the dependencies from the main autokey package. I'm glad it worked out :)
sebastiansam55 commented on 2020-12-02 21:16 (UTC)
This package needs to be split into Gtk and Qt versions. If you install this package and intend to use it on Qt based systems you MUST install the optional dependencies.
F-D commented on 2020-12-02 05:33 (UTC) (edited on 2020-12-02 05:35 (UTC) by F-D)
Hi I Can't use autokey on a XFCE Manjaro (patched as well as not-patched) "Error starting interface. Keyboard monitoring will be disabled. Check your system/configuraton. Can't connect to display ".0.0":b 'invalid MIT-MAGIC-COOKIE-1 key"
and after
"Fatal error strating AutoKey. 'Service' object has no attribute 'phraseRunner"
JoeSchr commented on 2020-11-29 12:50 (UTC) (edited on 2020-11-29 12:51 (UTC) by JoeSchr)
Hi, would it be possible to at this dependency:
python-qscintilla-qt5
It was missing and because of this
autokey-qt
wasn't working. See here: autokey/issues/475Thanks and great work!
EDIT: Ah sorry, I just saw, it's alread in optional dependencies, sorry about that
lateparty commented on 2020-11-13 00:19 (UTC)
@yochananmarqos yes please! thank you. I feel like I'm going to see a dark saber on the Mandalorian again before I get a response from the package owner here :(
yochananmarqos commented on 2020-11-12 21:39 (UTC)
I fixed my PKGBUILD if anyone is interested.
lateparty commented on 2020-10-17 14:19 (UTC)
@dark-saber using the current version, and did a rebuild, and I am still experiencing Traceback issues when opening autokey-qt from the terminal.
yochananmarqos commented on 2019-12-06 19:11 (UTC)
@dark-saber: I've updated my split-package PKGBUILD. It's actually proper this time and mimics the contents of the Debian packages of the same names. The only way I can see to avoid duplicate / conflicting files is to remove them manually.
dark-saber commented on 2019-11-19 00:05 (UTC)
ronjouch:
Yes, I've run into that with yay. Clearing the pkgdest or using
yay -S --rebuild autokey
seems to do the trick for me.ronjouch commented on 2019-11-18 02:36 (UTC)
Thanks @dark-saber.
I had rebuilt and it didn't solve the issue. I guess my AUR helper (yay) must maintain a cache and the simple rebuild I did must have failed to bust its cache.
Anyway, problem addressed with 0.95.8-2 :)
dark-saber commented on 2019-11-17 23:48 (UTC)
Thanks, ectospasm.
Yeah, usually you have to rebuild all foreign (AUR) python packages after major python upgrades.
pacman -Qqm
may be helpful.I've bumped the pkgrel to make sure everyone has rebuilt the package, but if I understand it correctly the philosophy of AUR is it's a user's responsibility to rebuild packages after the updates of their dependencies.
ectospasm commented on 2019-11-17 23:31 (UTC)
I changed directory to ~/.local/share/pikaur/aur_repos/autokey, and ran
makepkg -sri
to rebuild the package. That worked. This upstream issue defines the problem @ronjouch and I were getting:https://github.com/autokey/autokey/issues/323
Make sure you rebuild the package. Apparently my AUR helper (
pikaur
) wasn't doing that properly after the change to Python3.8.ronjouch commented on 2019-11-17 19:12 (UTC)
Same issue as user ectospasm since Arch's Python 3.8 upgrade. Re-building the package from PKGBUILD does not address the issue.
ectospasm commented on 2019-11-17 02:31 (UTC) (edited on 2019-11-17 02:32 (UTC) by ectospasm)
I'm getting a traceback when launching
autokey-gtk
:yochananmarqos commented on 2019-11-11 18:01 (UTC)
@Dr-Bracket: You're missing
python-qscintilla-qt5
.dginovker commented on 2019-11-11 17:58 (UTC)
dark-saber, I don't quite understand your comment on how you fix autokey-qt. What packages should I additionally install to fix the following issue?
ImportError: cannot import name 'Qsci' from 'PyQt5' (/usr/lib/python3.7/site-packages/PyQt5/__init__.py)
dark-saber commented on 2019-11-08 23:48 (UTC)
yochananmarqos:
Thank you! I guess most of this should be fixed now.
python-setuptools was moved to deps per fzzy's report on 2019-07-20 07:31.
I'll look into splitting the package slightly later, I wanted to do it for long enough, but the last time I've tried to do that it appeared to be less trivial than I expected.
yochananmarqos commented on 2019-11-05 20:51 (UTC) (edited on 2019-11-05 20:54 (UTC) by yochananmarqos)
@dark-saber: Why not create a split package?
autokey-common
as base andautokey-gtk
/autokey-qt
as meta packages with the corresponding dependencies? See my preliminary PKGBUILD.FYI,
python-six
is not necessary as it's required bypython-xlib
. Same withhicolor-icon-theme
,gtk-update-icon-cache
requires it.It appears
qt5-svg
is missing, see here.dark-saber commented on 2019-10-07 10:59 (UTC)
FrederickZh:
python-qscintilla-qt5 is in optdeps. That's not ideal, because it requires the manual intervention if you need autokey-qt, but it's only one time. The main problem is the main GUI of autokey is GTK, it was built around it initially, and Qt support was broken for prolonged time and restored only recently. And we can create a separate autokey-qt package, but the only difference it would have the Qt optdeps becoming deps; I guess, we won't be able to remove any of the GTK deps.
FrederickZh commented on 2019-10-06 15:41 (UTC)
It seems that autokey-qt needs python-qscintilla-qt5 to run. Otherwise it exits with an
ImportError: cannot import name 'Qsci' from 'PyQt5' (/usr/lib/python3.7/site-packages/PyQt5/__init__.py)
error.dark-saber commented on 2019-07-21 12:11 (UTC)
fzzy: Fixed, thank you!
fzzy commented on 2019-07-20 02:31 (UTC)
the package is missing a dependency: extra/python-setuptools
resulting in error:
Traceback (most recent call last): File "/usr/bin/autokey-gtk", line 6, in <module> from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources'
dark-saber commented on 2019-05-01 21:13 (UTC)
ectospasm: For monitoring I'm just using the Update Scanner extension for Firefox for now. That's not ideal, I wanted to switch to something better, but too many projects are not on Github (yet? I see a certain trend), so I end up monitoring some random page with a changelog. For GitHub projects, I have some ugly script that downloads the latest release from Releases page, tries to build it and runs namcap, but that doesn't always work, sometimes people change the base filename or compression method over releases, sometimes they publish the latest releases not on GitHub, but in other places for whatever reason. Then I'm looking through the changelog and run the app (or app that uses the library) manually to check if it's broken, unless that's some minor release of a Python/Ruby library.
ectospasm commented on 2019-04-30 23:36 (UTC)
dark-saber: Nope, I missed something. In all the hubbub I had forgotten that I actually uninstalled the AUR package (the setup.py install method won't work otherwise). When I didn't see the update come across in my (pikaur) package list, I was alarmed and thought it hadn't updated. Hence my message.
I guess you have a script that polls GitHub for a new release so it builds automatically? Just curious on how that works.
dark-saber commented on 2019-04-30 11:30 (UTC)
ectospasm: The package was updated to 0.95.7 two hours before your comment. Did I miss something?
ectospasm commented on 2019-04-29 21:36 (UTC)
Version 0.95.7 was released by the upstream developer TODAY (2019-04-29). Please update the AUR accordingly, it contains a fix I need (bugfixes/issue_257).
ectospasm commented on 2019-02-12 02:35 (UTC) (edited on 2019-02-12 02:45 (UTC) by ectospasm)
This package should be renamed to
autokey
, asautokey-py3
has been merged upstream (autokey
is written in Python3 now).Also, there is an upstream branch (https://github.com/autokey/autokey/tree/bugfix/issue_257) which fixes an Xlib.error.BadAtom error I encountered with the AUR package released 2019-02-10T10:50 -05:00. I will be eagerly awaiting for upstream to merge this fix with master. The BadAtom error breaks the X loop for autokey, rendering at least typed abbreviations useless.
The upstream developer was EXTREMELY responsive. They gave an initial response within seconds of my post, and within 24 hours the bugfix was applied to a branch. I am extremely impressed by this.
D_Schwartfeger commented on 2018-10-25 02:15 (UTC)
Information for other users of KDE/oxygen-gtk: On Manjaro KDE with GTK3 theme oxygen-gtk the 'Main Window' doesn't display properly and I have to start with something like "GTK_THEME=Adwaita:Manjaro autokey-gtk". I don't know if this a problem with oxygen-gtk or Autokey. If anyone can help I could send verbose logging info.
dark-saber commented on 2018-08-08 15:29 (UTC)
Alright, with some more patching python-atspi becomes an optional dep again.
But if you need ATSPI on Gtk interface, you still have to install the python-atspi-git package, the error messages are silenced, but the package from extra/ won't work.
dark-saber commented on 2018-08-08 15:05 (UTC)
Python-atspi is broken in Arch at the moment, see https://bugs.archlinux.org/task/59547.
The git version of python-atspi is currently the same 2.26.0 version with the added fix to the async problem from https://gitlab.gnome.org/GNOME/pyatspi2/merge_requests/3. It should replace the extra/python-atspi without major issues.
I guess we'll have to keep the current state of things till the new release of pyatspi with the fix merged or till the package in extra/ gets patched, whichever comes first.
zerophase commented on 2018-08-08 14:43 (UTC)
The issue with python-atspi is the git version needs to be released? I can't swith atspi versions as my gui needs the arch atspi. Have you tried getting the python-atspi maintainer to patch their version with the change needed?
D1ceWard commented on 2018-08-08 08:22 (UTC) (edited on 2018-08-08 08:40 (UTC) by D1ceWard)
Can't remove python-atspi since it's used for my graphical interface (cinnamon)
But as you said Qt version work fine
DaveB commented on 2018-08-08 06:42 (UTC)
Works for me now, thanks!
dark-saber commented on 2018-08-07 17:58 (UTC)
Thanks for the reports! Yes, the package should be reinstalled after major python update like most other AUR python packages.
Regarding atspi error, I believe, this should be reported upstream. Python-atspi will be in conflicts array till the issues are resolved. autokey-qt didn't fail for me after quick testing, autokey-gtk worked too if you remove python-atspi. If you'll find some more issues, please let me know.
DaveB commented on 2018-08-07 07:28 (UTC)
After getting the same error as below (re autokey==0.95.2) and updating, I now get the following error.
prosoitos commented on 2018-08-06 23:57 (UTC) (edited on 2018-08-07 00:02 (UTC) by prosoitos)
Same here. Broke with python updates.
Other apps broke with the same error message.
xardover commented on 2018-08-06 20:47 (UTC)
Broke with latest python updates
Batou commented on 2018-05-12 05:41 (UTC) (edited on 2018-05-12 05:43 (UTC) by Batou)
@cmad, maintainer on the github changed some files to fix a bug. Change 1st hash to d891c446d6413954c45db8f32ab4fc0db6022f1fabf7d163350137b25a279154
cmad commented on 2018-05-11 23:15 (UTC)
I'm getting an integrity error with v0.94.0.tar.gz The sha256 doesn't seem to match for it.
wallace11 commented on 2018-04-29 17:02 (UTC)
Manjaro KDE doesn't export locale properly so in order to run autokey-gtk you must first export your locale via export LC_ALL="en_US.UTF-8"
jfk commented on 2017-12-15 23:14 (UTC)
@dark-saber: ok thank you for your reply, I'll have an eye on further developments.
dark-saber commented on 2017-12-14 06:12 (UTC)
jfk: Are you trying to run autokey-qt or autokey-gtk? Could you please try to execute autokey-gtk from the terminal and see if there is any useful output.
Autokey-qt is broken for a long time, because new versions of Plasma don't support PyKDE4, which it was based on, and PyKDE4 packages were removed from Arch repos. I see xuzhao9 is working now on PyQt5 port (https://github.com/autokey-py3/autokey/network), I hope he would make it, but for now we are stuck with GTK interface.
jfk commented on 2017-12-13 21:43 (UTC)
KDE Plasma 5.40.0 lts 4-9.68 nothing opens.
"qr-at-spi" is installed.
dark-saber commented on 2017-10-31 21:31 (UTC)
franga2000 commented on 2017-10-31 12:59 (UTC)
a-bostaurus commented on 2017-10-07 08:30 (UTC)
dark-saber commented on 2017-10-04 07:21 (UTC) (edited on 2017-10-04 07:26 (UTC) by dark-saber)
a-bostaurus commented on 2017-10-04 07:05 (UTC)
a-bostaurus commented on 2017-09-25 06:05 (UTC)
dark-saber commented on 2017-09-22 11:03 (UTC)
a-bostaurus commented on 2017-09-22 08:17 (UTC) (edited on 2017-09-22 08:22 (UTC) by a-bostaurus)
dark-saber commented on 2017-02-23 06:49 (UTC)
elbowz commented on 2017-02-22 13:07 (UTC)
dark-saber commented on 2017-01-14 15:20 (UTC)
Hal5000 commented on 2017-01-13 09:34 (UTC)
ronjouch commented on 2017-01-12 22:55 (UTC) (edited on 2017-01-12 23:35 (UTC) by ronjouch)
snuffop commented on 2017-01-12 17:46 (UTC) (edited on 2017-01-12 17:47 (UTC) by snuffop)
dark-saber commented on 2017-01-12 15:30 (UTC)
snuffop commented on 2017-01-12 14:15 (UTC)
troxor commented on 2017-01-05 17:51 (UTC)
nfs commented on 2016-12-30 03:40 (UTC)
dark-saber commented on 2016-12-26 19:13 (UTC)
ant commented on 2016-12-26 16:48 (UTC)
nfs commented on 2016-12-24 18:29 (UTC) (edited on 2016-12-30 03:40 (UTC) by nfs)
dark-saber commented on 2016-12-24 14:09 (UTC)
nfs commented on 2016-12-23 17:44 (UTC)
dark-saber commented on 2016-12-22 07:58 (UTC) (edited on 2016-12-23 16:43 (UTC) by dark-saber)
nfs commented on 2016-12-21 20:17 (UTC) (edited on 2016-12-22 15:01 (UTC) by nfs)
dark-saber commented on 2016-12-21 09:38 (UTC)
nfs commented on 2016-12-21 08:36 (UTC)
dark-saber commented on 2016-10-28 07:35 (UTC)
sdothum commented on 2016-10-27 01:35 (UTC)
elbowz commented on 2016-09-12 16:20 (UTC)
dark-saber commented on 2016-09-10 21:07 (UTC)
elbowz commented on 2016-09-08 11:03 (UTC)
dark-saber commented on 2016-08-14 18:13 (UTC)
cryzed commented on 2016-08-12 13:42 (UTC)
cryzed commented on 2016-08-10 18:58 (UTC) (edited on 2016-08-10 19:07 (UTC) by cryzed)
dark-saber commented on 2016-08-10 13:22 (UTC)
cryzed commented on 2016-08-08 20:54 (UTC) (edited on 2016-08-08 21:59 (UTC) by cryzed)
cryzed commented on 2016-06-18 12:27 (UTC)
dark-saber commented on 2016-06-18 08:00 (UTC)
D_Schwartfeger commented on 2016-06-17 21:41 (UTC)
dark-saber commented on 2016-05-22 06:27 (UTC)
MagicAndWires commented on 2016-05-20 22:54 (UTC)
ectospasm commented on 2016-04-23 12:47 (UTC)
flyhunter commented on 2015-12-29 20:56 (UTC) (edited on 2016-01-03 21:05 (UTC) by flyhunter)
dark-saber commented on 2015-11-24 16:29 (UTC)
DaveB commented on 2015-11-23 20:21 (UTC)
nhasian commented on 2015-07-29 23:12 (UTC)