Arch Linux User Repository

@yochananmarqos Thank you for implementing this change which will save all users of moderm Python 3.14 from using a crippled Autokey.

Python is not the python it was when Autokey was first written. Therefore this update is essential because without it Autokey cannot be used with modern python 3.14.

Is the code intended to be depricated permanently? Obviously, no. If the ccode is intended to be deprecated permanently then the existance of this reporting forum comes into question.

Since this reporting forum is here we can clearly determine necessary updates can be reported and actioned.

Here is an update that keeps the code backwards compatiable if that is desired.

try: # This works for Python 2.6 through Python 3.14+ text = model.get_value(next(i).iter, 0) except TypeError: # Fallback for Python 2.5 and older (where 'next()' isn't a builtin) text = model.get_value(i.next().iter, 0)

Thank you

@kes: Thanks for the heads up, I've added a patch.

@dreieck: No. When one uses AUR packages, they are responsible for maintaining them on their own system. That includes rebuilding them on newer libraries / major Python versions when required.

@tosts NEVER symlink incompatible libraries. They're versioned for a reason. Now you've got people in upstream issues parroting your erroneous "solution" confusing the developers.

SOLUTION

For a very long time I could not update abbreviations for phrases within the Autokey GUI. I could only achieve this by - creating phrases through creating paired backend .txt and .json text files for each phrase, and - adjusting these paired files as necessary within the backend to meet my requirements using nvim for each phrase file pair.

This was very inconvenient.

THE SOLUTION:

I am running Python 3.14. which has has fully deprecated the .next() method on Gtk Iterators, which causes the phrases and abbreviations dialogs to crash with an AttributeError. I've verified that replacing i.next() with next(i) fixes the issue while maintaining backward compatibility.

Specifically line 336 of file

/usr/lib/python3.14/site-packages/autokey/gtkui/dialogs.py

is incompatiable with Python 3.14 and has to be changed from

text = model.get_value(i.next().iter, 0)

to

text = model.get_value(next(i).iter, 0)

I have used this bash command to make the change sudo sed -i 's/i.next().iter/next(i).iter/g' /usr/lib/python3.14/site-packages/autokey/gtkui/dialogs.py

After I made the above change phrases can again be created and abbreviations adjusted using the Autokey GUI.

Can you increment $pkgrel so that it get's recognised as an update and rebuilt?

Need to re-package for new python version:
Needs to be rebuilt (and $pkgrel increased) because modules are still built for outdated python version:

Traceback (most recent call last):
  File "/usr/bin/autokey-qt", line 5, in <module>
    from autokey.qtui.__main__ import Application
ModuleNotFoundError: No module named 'autokey'

Traceback (most recent call last):
  File "/usr/bin/autokey-gtk", line 5, in <module>
    from autokey.gtkui.__main__ import main
ModuleNotFoundError: No module named 'autokey.gtkui'

Traceback (most recent call last):
  File "/usr/bin/autokey-qt", line 5, in <module>
    from autokey.qtui.__main__ import Application
ModuleNotFoundError: No module named 'autokey.qtui'

(Applies to all packages of this split package: autokey-common, autokey-gtk, autokey-qt.)

Regards!

autokey-common installs into /usr/lib/python3.12, but there is a /usr/lib/python3.13 now. (So autokey-gtk no longer find's it's module.)

(Can be worked around with a symlink.)

Note that this problem only affects autokey-gtk. Autokey-qt works normally.

Yes. I have had this problem for a few months now and use the same workaround as you. Things used to work fine for years before this started.

I am running autokey-gtk, latest version, and may have identified a bug.

Autokey-gtk functions, but with some workarounds. The bit that is not working is I am not able to
(1) rename phrases within the Autokey interface menus or
(2) set abbreviations within the Autokey interface menu / pop-ups

I can however work around this by exiting the Autokey app, and creating new files within folder
"/home/$USER/.config/autokey/data/My Phrases/Address - Home"
editing these, then re-starting Autokey, which then sucks the new files up.
But this is a bit messy.
These new files are then shown in the Autokey interface, but are not editable from within the Autokey interface.

My file write accesses look Ok.

I can duplicate files using the Autokey menu but that is it.

Anyone else seen this?

Thank you yochananmarqos. Working for me now too.

thank you, it's working, Appreciated :)