Arch Linux User Repository

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.

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

I just copied the dependencies from the main autokey package. I'm glad it worked out :)

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.

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"

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/475

Thanks and great work!

EDIT: Ah sorry, I just saw, it's alread in optional dependencies, sorry about that

@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 :(

I fixed my PKGBUILD if anyone is interested.

@dark-saber using the current version, and did a rebuild, and I am still experiencing Traceback issues when opening autokey-qt from the terminal.

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

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.