Autokey on Manjaro Linux?

[Jeffrey Needle]

Manjaro is an Arch-based distro. Works so well on my old hardware.
Autokey is not in the distros. I'm something of an idiot when it comes
to things like this. How can I get autokey onto my new system? Thanks.

[Joe]

For starters, see:

https://code.google.com/p/autokey/wiki/InstallingAutoKey

See the section, "Other Linux Versions".

It was written with inexperienced users in mind, although it also has
more concise instructions.

See how far you can get and then post back here if you get stuck.

If you do get stuck, try to include details of your OS version, desktop,
exactly what you did, and any error messages you got so we have what we
need to analyze the problem.

Joe

P.S. Keith, the person who wrote this document, is a big fan of Arch and
he has run AutoKey on it, so, barring any release specific issues, it
should work.

[Steve Fisher]

Just run:
yaourt autokey

And pick the one you need, I run Manjaro and autokey-gtk

Steve

[Jeffrey Needle]

I did that, and autokey now installs in the Manjaro menu, but when I
click on the entry in the start menu (or whatever it's called), nothing
seems to happen. I used to get a blue A in the taskbar at the bottom of
the screen (when using other distros). Am I missing someting here?
Thanks.

> --
> You received this message because you are subscribed to the Google
> Groups "autokey-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to autokey-user...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Jeffrey Needle]

Thanks, I'll give it a try.

[Joe]

Click on the Blue A in your taskbar to bring up the AutoKey menu.

That will allow you to configure AutoKey and to define macros, etc.

You should also verify what version of AutoKey is installed. At this
point, it will probably be the latest one (I think it's 0.90.4). If not,
you will probably want to upgrade it to get all the latest fixes and
enhancements. Help->About AutoKey should tell you.

Joe

I don't have it running now, but I think hovering over it and right
clicking on it produce additional information and options.

[Jeffrey Needle]

But, as I stated, there is no blue A in the taskbar! I know how that
works from other distros. I must be doing something wrong in installing
it. It asks a slew of questions about editing this file and that. I've
said "no." Perhaps I'm missing some dependencies that are required
here?

[Joe]

Oops. Misread your post. I thought I had seen a number of post from you
in the past (i.e. You are an experienced user.)

Do the standard bug dance:
Open a console (terminal window) gnome-terminal, xterm, konsole - which
ever one you have installed
Run your version of autokey with the -l (ell) option which makes autokey
tell us what it's doing in more detail and copy and paste the results to
a post here.

autokey-gtk -l
or
autokey-qt -l

Joe

[Jeffrey Needle]

No, you're correct, I am an experienced user of autokey. But it's
always been run before on Debian/Ubuntu-based distros. I have a box
running Manjaro Linux (Arch-based). And while autokey is apparently in
the Arch repositories, it isn't in the Manjaro repos. That's my
problem.

Here's the output. I don't know it tells us much. Thanks.

[jeff@jeff ~]$ autokey-gtk -l
Traceback (most recent call last):
File "/usr/bin/autokey-gtk", line 20, in <module>
from autokey.gtkapp import Application
File "/usr/lib/python3.3/site-packages/autokey/gtkapp.py", line 80
except Exception, e:
^
SyntaxError: invalid syntax
[jeff@jeff ~]$ ^C

[Joe]

I'm no flash with Python, but I believe the last version of Python on
which AutoKey was tested was Python 2.7 and you appear to be running
Python 3.3.

Although a lot of syntax changed between version 2.x and 3.x, 3.x is
still supposed to run 2.x code.

I would guess you either have to tell Python that AutoKey is written in
Python 2.7 or you have to find a way to get it to use the Python 2.7
libraries when it runs.

I don't know how to do either, but someone else on this list probably does.

Until we get a better answer, try:
ls /usr/bin | grep 'python2.7'

If it finds it, try,

python2.7 autokey-gtk -l

and see what happens.

I don't know if that's enough magic for Python to fully use 2.7 instead
of 3.3, but it's worth a try.

Joe

[Jeffrey Needle]

Strange output:

[jeff@jeff bin]$ python2.7 autokey-gtk -l

Traceback (most recent call last):

File "autokey-gtk", line 20, in <module>
from autokey.gtkapp import Application
ImportError: No module named autokey.gtkapp

What does this mean? Thanks for your help.

[Joe]

Not enough magic. Died at the same place, but looks like the first
attempt got further. It found the (probably) wrong module and now we
didn't find the module at all.

From here on in, I'm purely guessing. Make appropriate backups before
changing anything!

Just for giggles, do
`
ls -l /usr/share/pyshared/autokey/
ls -l /usr/lib/python2.7/dist-packages/autokey
ls -l /usr/lib/python3.3/dist-packages/autokey


That's where some of these things live. Maybe they got installed under
/usr/lib/python3.3/
instead of under /usr/lib/python2.7/

If so, we could try making a symlink and see what happens
sudo ln -s /usr/lib/python3.3/dist-packages/autokey
/usr/lib/python2.7/dist-packages/autokey

If that fixes it, we can actually move them there.

My hope is that maybe whoever packaged autokey for your distro figured
it was good to go for Python 3.3 and installed it there.

If it's that simple, then you can just uninstall autokey in your package
manager and install it manually. I'm looking into how to do that.

Joe

[Jeffrey Needle]

Thanks so much for all of this. After a dinner and a rest, I've decided
that I'm in for a lot of trouble in the future if I stick with an
Arch-based distro. So much of my life is tied up in Debian-based
distros. to my great sadness, I've crashed the computer and installed a
Deb-based distro. I'm too old to be messing with things life this. <grin>

I'm grateful for all the help I've received here. Thanks.

[Joe]

From what I've heard, arch is a very good distro (and I assume Manjaro
is too), but AFAIK, distros like this, slackware, and gentoo are geared
toward people who want or need to get more into the internals of Linux
and optimizing it for their particular needs. They are not Linux from
scratch, but they're not for the faint of heart either. Debian based
distros are a bit more user friendly and they're much more preconfigured
to "just work".

Just curious, which distro did you choose? From what I hear Linux Mint
is very good and it comes in several preconfigured versions for
different desktop environments like KDE, LXDE, and Cinnamon.

Best of luck.

Joe

[Joe]

You don't have to just give up. You can always dual boot or put Manjaro
in a VM. That way, you can still get things done while tinkering at your
leisure with the new distro.

I'm going to have to upgrade my OS shortly. I'm still on kubuntu 12.04
and that's pretty old.

I plan to copy my root partition to another partition and do the
upgrades there without touching my current "production" partition. I
already have /home on its own partition, so with a few backups, I should
be able to use it with both the old and new distros.

Joe

On 12/16/2013 03:54 AM, Jeffrey Needle wrote:

[Jeffrey Needle]

I've used many distros over the years, from pure Debian to Ubuntu to
Mint to Bodhi, etc. I discovered LXLE about nine months ago, and I've
found myself going back to it. It's an Ubuntu-based distro using the
LXDE desktop. Just gorgeous -- best desktop backgrounds I've ever seen.
And it just works. So that's where I'm at right now.

Thanks again for all the help.

[Jeffrey Needle]

Unfortunately, I'm on a very old Dell desktop with an 80 gig drive, and
I need all the room I can get. Dual booting, although possible, is just
not practical right now. But thanks for the idea.

[Dave Blair]

I've had that problem on several Arch installations.

There's a missing dependency in the PKGBUILD installation file, I can't
remember what it is, sorry � some python2 bindings package or something
� but you'll see it when you run autokey from the terminal. Yaourt that
dependency, pkill any autokey instances you might still have running,
and you should be good to go.

Ok that's weird: Curiosity got the better of my and I tried installing
autokey in a test Manjaro VM, worked perfectly without this dependency
problem... strange.

Best, Dave

[Jeffrey Needle]

Okay, I'm totally wierded out.

I just reinstalled Manjaro from scratch. Issued "yaourt autokey" from
terminal. It installed perfectly! I'm happy!!!! I'm able to use
Manjaro now for everyday use!

Thanks so much.

[Joe]

Great!

Joe