Skip to content

Installing from GitHub

Joe edited this page Sep 1, 2016 · 10 revisions

You may want to consider upgrading to the latest version of AutoKey. It may not directly affect your current issue, but fixes, if any, will be applied to that version and your trace log will be easier for the developers to work with.

  1. Backup everything in $HOME/.config/autokey to somewhere out of the way in case anything gets damaged and needs to be restored

  2. Install git if it's not already installed

    sudo apt-get install git

  3. Create a directory (anywhere you want it) for the source code and change into it. For example:

    mkdir ~/installs/autokey cd ~/installs/autokey

  4. Clone the code from GitHub onto your local drive

    git clone https://github.com/autokey/autokey

  5. From the INSTALL file:

The full application can be installed using the setup script: python setup.py install

Change directories into the autokey directory created by git clone before running it.

cd autokey

It appears that running setup.py does not install the dependencies AutoKey needs to run. You will have to do that manually.

This is a tentative list of packages you may need to manually install (for the autokey-qt version):

python-dbus
python-qt4
python-dbus-dev
python-qt4-dev
python-qt4-dbus
python-kde4
python-xlib
python-pyinotify
pyqt4.qsci-dev
python-qscintilla2
python-appindicator

Alternatively, you can build Debian packages using the following command:

dpkg-buildpackage -us -uc
cd ../

Then to install the GTK version:

sudo dpkg -i autokey-gtk_<version>.deb autokey-common_<version>.deb

Or the Qt version:

sudo dpkg -i autokey-qt_<version>.deb autokey-common_<version>.deb

I went with the dpkg method instead of just the setup method.

  1. Check the installed version of AutoKey

    dpkg -s autokey-common | grep Version

This should output:

Version: 0.90.4-1

so we know the latest version did get installed. This will only work if you went the dpkg route in the steps above.

  1. Make sure autokey is not running and then run it from a terminal

  2. Make sure everything works (or is broken) just like it was before you started.

We need to know that everything is OK before making any changes.

Now we have a "working" base system.

Clone this wiki locally