Package Base Details: autokey

Git Clone URL: https://aur.archlinux.org/autokey.git (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 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

wallace11 commented on 2018-04-29 17:02

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

@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

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

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

franga2000:
Added it, thanks!

franga2000 commented on 2017-10-31 12:59

The qt-at-spi (AUR) package is required to make this work in KDE. This should probably be added to optdepends

a-bostaurus commented on 2017-10-07 08:30

Thank you. I did as you proposed. Some years ago I had this problems, too.

dark-saber commented on 2017-10-04 07:21

I'm just maintaining the package for Arch and I'm capable to solve packaging problems mostly (missed dependencies, that kind of stuff). Your issue should be addressed to developers: https://github.com/autokey-py3/autokey/issues. Here's the problem reporting guide: https://github.com/autokey/autokey/wiki/Problem-Reporting-Guide, it would be better to run autokey via "autokey-gtk -l" and attach the logs.

By the way, I'm on kernel 4.13.4 / XFCE / nvidia, and abbreviations seemingly work for me.

a-bostaurus commented on 2017-10-04 07:05

What does that mean: "This should probably be reported upstream." How can I do this?

a-bostaurus commented on 2017-09-25 06:05

I think the working of autokey depends not only on kernel 4.12 or 4.13 but also on the graphic utilities. My desktop computer is with intel: Autokey is okay with 4.13. My notebook is with nvidia; autokey does not work with 4.13.