Author Topic: Autokey stopped working after updates.  (Read 678 times)

Offline veronicathecow

  • Full Member
  • ***
  • Posts: 192
Re: Autokey stopped working after updates.
« Reply #15 on: February 14, 2013, 02:25:24 PM »
Hi sorry, yes Re-installed and then rebooted

Offline pinoc

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2880
    • other projects...
Re: Autokey stopped working after updates.
« Reply #16 on: February 14, 2013, 03:13:30 PM »
which DE is this: KDE, LXDE, XFCE,...?

Could you try to create a new user-account and see if it fails there as well?

Offline veronicathecow

  • Full Member
  • ***
  • Posts: 192
Re: Autokey stopped working after updates.
« Reply #17 on: February 14, 2013, 03:22:16 PM »
Hi Pinoc, KDE. Tried with new user, same result and error messages.

Offline JohnW_57

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2252
Re: Autokey stopped working after updates.
« Reply #18 on: February 14, 2013, 03:37:26 PM »
Tested on 64 bit and working here.

Got this on 1st start:

Code: [Select]
[wim@localhost ~]$ autokey-qt
Xlib.protocol.request.QueryExtension
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 15, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 16, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 17, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 18, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 19, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 20, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 21, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 22, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 23, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 24, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 25, major_opcode = 33, minor_opcode = 0
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 603, sequence_number = 26, major_opcode = 33, minor_opcode = 0
Xlib.protocol.request.QueryExtension
autokey(26508) KXMLGUIClient::setXMLFile: cannot find .rc file "autokeyui.rc" for component "autokey"
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x4a000d7


2nd start was without any messages.

JohnW
PCLinuxOS 2013 KDE4 (64 bit) on: home build system:  Intel Core 2 Quad (q6700) (2.66ghz), Asus P5K motherboard, 4 gig ddr2 memory, Asus Nvidia Geforce GTS 250 1024 mb gddr3, Crucial M4 128 SSD,  2x Samsung 500 gig HDD (sata), TSSTcorp CDDVDW SH-224BB.

Offline veronicathecow

  • Full Member
  • ***
  • Posts: 192
Re: Autokey stopped working after updates.
« Reply #19 on: February 14, 2013, 03:45:20 PM »
Hi JohnW, thanks for trying. The error message I am getting is different.
RuntimeError: the sip module implements API v9.0 to v9.1 but the PyKDE4.kdecore module requires API v8.1

Offline JohnW_57

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2252
Re: Autokey stopped working after updates.
« Reply #20 on: February 14, 2013, 03:49:09 PM »
Also tested on 32 bit with the same results.

JohnW
PCLinuxOS 2013 KDE4 (64 bit) on: home build system:  Intel Core 2 Quad (q6700) (2.66ghz), Asus P5K motherboard, 4 gig ddr2 memory, Asus Nvidia Geforce GTS 250 1024 mb gddr3, Crucial M4 128 SSD,  2x Samsung 500 gig HDD (sata), TSSTcorp CDDVDW SH-224BB.

Offline veronicathecow

  • Full Member
  • ***
  • Posts: 192
Re: Autokey stopped working after updates.
« Reply #21 on: February 14, 2013, 03:52:15 PM »
Curious.
Wish I had the time and brains to become a packager then i could perhaps re-compile and sort problems like this.

Offline JohnW_57

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2252
Re: Autokey stopped working after updates.
« Reply #22 on: February 14, 2013, 04:02:30 PM »


This is what I get on my system.

JohnW
« Last Edit: February 14, 2013, 04:04:07 PM by JohnW_57 »
PCLinuxOS 2013 KDE4 (64 bit) on: home build system:  Intel Core 2 Quad (q6700) (2.66ghz), Asus P5K motherboard, 4 gig ddr2 memory, Asus Nvidia Geforce GTS 250 1024 mb gddr3, Crucial M4 128 SSD,  2x Samsung 500 gig HDD (sata), TSSTcorp CDDVDW SH-224BB.

Offline veronicathecow

  • Full Member
  • ***
  • Posts: 192
Re: Autokey stopped working after updates.
« Reply #23 on: February 14, 2013, 04:13:28 PM »
Hi John, yup that's what I was getting for a few days before some update went and killed it. I got used to having the facility and then it was cruelly snatched from my grasp!
Such a useful little program.

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 11054
  • MLUs Forever!
Re: Autokey stopped working after updates.
« Reply #24 on: February 14, 2013, 05:34:27 PM »
Hi JohnW, thanks for trying. The error message I am getting is different.
RuntimeError: the sip module implements API v9.0 to v9.1 but the PyKDE4.kdecore module requires API v8.1

All I could suggest is to reinstall the following

pykde4                  (ver 4.9.5)

python-kde4          (ver 4.6.0)

kdelibs                  (ver 4.9.5)

I would do them one at a time and check the application after each.
MLUs rule the roost!

Linux XPS 3.4.48-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Offline pinoc

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2880
    • other projects...
Re: Autokey stopped working after updates.
« Reply #25 on: February 15, 2013, 12:15:11 AM »
there is another potential cause for the failure: do you use PASS or a public mirror?

The reason I'm asking is that all latest packages are on PASS but some packages are not yet on the public mirrors and this could cause your error. 
-p.

Offline veronicathecow

  • Full Member
  • ***
  • Posts: 192
Re: Autokey stopped working after updates.
« Reply #26 on: February 15, 2013, 01:06:19 AM »
Hi Pinoc, I use a public mirror.
Just17, you have cracked it. I did a re-install of pykde4, started the app and it works fine now. Have also done a reboot and still fine.
Many thanks to you all for your help it is very much appreciated.  :)
Now put your tin hats on in case any more meteorites decide they want to visit planet earth this morning!