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 .. 5 6 7 8 9 10 11 12 13 14 Next › Last »

tpaniaki 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.

tpaniaki 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: Added it, thanks!

franga2000 commented on 2017-10-31 12:59 (UTC)

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

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

dark-saber commented on 2017-10-04 07:21 (UTC) (edited on 2017-10-04 07:26 (UTC) by dark-saber)

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

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

a-bostaurus commented on 2017-09-25 06:05 (UTC)

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.

dark-saber commented on 2017-09-22 11:03 (UTC)

a-bostaurus: This should probably be reported upstream. I've tried it on Arch Linux testing now (Linux 4.13.3, XFCE) and, although I've ran into some other problems (pasting using Mouse Selection just hangs; no non-latin input using Keyboard method; phrase list doesn't refresh automatically after modifying it using scripts, had to restart the app to refresh), I guess I didn't encounter yours. I've found the only issue that might be remotely related to yours: https://github.com/autokey-py3/autokey/issues/95 There may be something in the debug logs too.

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