autokey-qt Unaccessible and Using 100% processor After Logout/Login (as startup app)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autokey (Ubuntu) |
Confirmed
|
Critical
|
Unassigned |
Bug Description
autokey-qt becomes unaccessible while using 100% processor after logging out and back into the Unity Desktop (when you have autokey-qt as a startup application).
To reproduce this bug, do the following:
1) Install autokey-qt:
sudo apt-get install autokey-qt
2) Add autokey-qt as a startup application:
Super-key > type "startup applications" > Add Name "Autokey (qt)" > Add Command "autokey-qt"
3) Restart Your Computer
4) Login, and notice autokey-qt starts up, and there will be a "A" icon indicator/applet near the clock
5) Logout of the Unity Desktop, and then log back in
You will get the following error:
AutoKey is already running as pid 2163 but is not responding
Details:
org.freedesktop
6) The AutoKey-qt process is actually running with 100% processor utilization, but the "A" icon indicator/applet is not even there (making autokey-qt unaccessible). You must reboot your computer in order to use autokey again, or kill the autokey-qt processes already running and launch autokey-qt again.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: autokey-qt 0.90.1-1.1
ProcVersionSign
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Mon Nov 5 22:35:15 2012
InstallationDate: Installed on 2012-10-19 (18 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: autokey
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in autokey (Ubuntu): | |
importance: | Undecided → Critical |
tags: | added: saucy |
Changed in autokey (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | removed: quantal |
Hi Lonnie,
Running an up-to-date 12.04.3 VM, I was not able to reproduce this issue after logging out and back in; autokey appears to be using a negligible amount of CPU.
Are you able to reproduce this on a system without custom configuration? If not, perhaps the issue is due to a misperforming script.