Arch Linux User Repository

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.

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.

fzzy: Fixed, thank you!

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'

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.

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.

ectospasm: The package was updated to 0.95.7 two hours before your comment. Did I miss something?

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

This package should be renamed to autokey, as autokey-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.

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.