Autokey 0.81.4 in Fedora 17

[Jeffrey Needle]

Hi.  Brand new install of Fedora 17 (the latest available).  Its software repository offers Autokey 0.81.4.

After creating one script and two abbreviations, I find that, after typing the trigger characters, the cursor moves the correct number of spaces/lines, as if it's expanding the text correctly, but it leaves only blank spaces.

Is this a known problem with Fedora?  Any way to fix it?

Thanks.

[Luke Faraone]

Consider reporting a bug against Autokey, slash seeing if any of https://bugzilla.redhat.com/buglist.cgi?product=Fedora&content=autokey describes your issue.  

--

Luke Faraone;; Debian & Ubuntu Developer; Sugar Labs; GMU 2014
lfaraone on irc.[freenode,oftc].net -- https://luke.wf/ohhello 
PGP fprint: 5189 2A7D 16D0 49BB 046B  DC77 9732 5DD8 F9FD D506

[Jeffrey Needle]

Done.  Perhaps someone else here can offer some insight.  I don't know how quickly they act on the bugzilla reports.

Thanks.

[Johnny Rosenberg]

2012/9/12 Jeffrey Needle <jeff....@gmail.com>:

> Done. Perhaps someone else here can offer some insight. I don't know how
> quickly they act on the bugzilla reports.
>
> Thanks.
>
>
> On Tue, 2012-09-11 at 20:17 -0400, Luke Faraone wrote:
>
> On 11 September 2012 19:45, Jeffrey Needle <jeff....@gmail.com> wrote:
>
> Hi. Brand new install of Fedora 17 (the latest available). Its software
> repository offers Autokey 0.81.4.
>
> After creating one script and two abbreviations, I find that, after typing
> the trigger characters, the cursor moves the correct number of spaces/lines,
> as if it's expanding the text correctly, but it leaves only blank spaces.
>
> Is this a known problem with Fedora? Any way to fix it?

0.81 is not exactly the newest version of AutoKey. Maybe there were
bugs that are corrected now?
Since AutoKey is written in Python, I guess it's not too much work to
install the newest one manually, but I'm sure someone else can guide
you better in that case.


Kind regards

Johnny Rosenberg
ジョニー・ローゼンバーグ

[jos...@main.nc.us]

Take a look at:

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

Those instructions are for debian based distros (using apt/dpkg).

You can do "Version C", steps 1 -7. That will get the package sources
downloaded and unpacked.

I don't know enough python, yum, fedora, ... to do the rest, but I'm sure
someone else on the list will fill in the details.

Joe

[jos...@main.nc.us]

Looks like it's available in fedora 18:

http://pkgs.org/fedora-rawhide/fedora-i386/autokey-gtk-0.90.4-2.fc18.noarch.rpm.html

[Jeffrey Needle]

<snip>

0.81 is not exactly the newest version of AutoKey. Maybe there were
bugs that are corrected now?
Since AutoKey is written in Python, I guess it's not too much work to
install the newest one manually, but I'm sure someone else can guide
you better in that case.


Kind regards

Johnny Rosenberg
ジョニー・ローゼンバーグ

Thanks.  Yes, Python is a mystery to me.  If the new version indeed works correctly, I would greatly appreciate any help anyone can offer.  Again, thanks for the note.

[Jeffrey Needle]

Trying to update doesn't work.  I'm guessing Fedora 17 needs to be updated, anyway.  Funny, I thought this was the latest version.  I'll need to update to Fedora 18.  I'll do it and get the newest autokey that way.

Thanks.

[Jeffrey Needle]

Well, it won't be until October until Fedora 18 is released.  I'll have to wait until then.

On Wed, 2012-09-12 at 15:17 -0400, jos...@main.nc.us wrote:

[Jeffrey Needle]

Okay, now I'm spooked.  Autokey is working fine.  I have no idea why it didn't work originally.  A reboot, maybe?  I did re-start the computer.

Sorry for all the fuss.  It's working now.

On Wed, 2012-09-12 at 15:17 -0400, jos...@main.nc.us wrote:

[Tom]

Installation is supposed to be as simple as extracting the files from the archive, then running

sudo python setup.py install

Unfortunately, 0.90.4 on Fedora 17 crashes with the following error:

gi.RepositoryError: Requiring namespace 'Gtk' version '2.0', but '3.0' is already loaded

 

[Ingo Hoffmann]

I have seen this problem in both Fedora 18 and 19. Is there a fix for this?