AutoKey-QT Missing Indicator After Launched as Startup Application

Bug #1160558 reported by Lonnie Lee Best
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Expired
Undecided
Unassigned
autokey (Ubuntu)
Expired
Undecided
Unassigned
unity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I run autokey-qt as a startup application, its indicator often doesn't appear on Unity's top-panel (by the clock).

Why can't I successfully run autokey-qt as a startup application? By running autokey-qt as a start up application, is it somehow getting launched before the Unity top-panel is initialized? I'm able to run other indicators as startup applications (such as indicator-weather, hamster-indicator, parcellite). So why not autokey-qt?

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 that autokey's "A" icon-indicator/applet near the clock is *MISSING*.

5) The indicator is missing, but you can verify that the autokey-qt process is indeed running with System Monitor:
Super-key > type "system monitor" > System Monitor > Processes tab > Process Name > autokey-qt

6) See attached screen shot below.

So as, you can see, autokey-qt is running, but there is no way to use it without that indicator.

Workaround: Kill the orphan autokey-qt process and launch it again manually. However, my goal is to start it automatically each time I login, and the process should be killed each time I logout (So, that I don't get an "Already Running" error after logout and logging back in).

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: autokey-qt 0.90.1-1.1
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Tue Mar 26 14:18:22 2013
InstallationDate: Installed on 2013-03-06 (20 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: autokey
UpgradeStatus: Upgraded to quantal on 2013-03-06 (20 days ago)

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :
summary: - AutoKey-QT Missing Indicator After Launch as Startup Application
+ AutoKey-QT Missing Indicator After Launched as Startup Application
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

In Ubuntu 13.04, so far, the indicator doesn't appear even if you launch autokey-qt manually.

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

This must of had to do with upgrading from 12.10 to 13.04.

Now that I've performed a fresh install of 13.04 beta, the indicator for Autokey-qt is back.

So, I suspect this bug is elusively related to those who do distribution upgrades.

tags: added: dist-upgrade
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

This bug remains an issue in Ubuntu 13.10.

I've upgraded from 13.04 to 13.10, and I am again experiencing this issue. Now I'm using autokey-gtk instead of autokey-qt.

For some reason, AutoKey's indicator never seems to be able to survive an Ubuntu upgrade.

tags: added: saucy
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: autokey-gtk 0.90.1-1.1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Thu Sep 5 22:06:22 2013
InstallationDate: Installed on 2013-08-03 (33 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: autokey
UpgradeStatus: Upgraded to saucy on 2013-08-28 (8 days ago)

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :
Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

I just reinstalled Ubuntu 13.10 from the daily build:
http://cdimage.ubuntu.com/daily-live/current/

This did NOT resolved the missing-indicator issue.

Please confirm this bug, and deem it critical.

Revision history for this message
Luke Faraone (lfaraone) wrote :

Lonnie,

Can you clarify whether you were able to experience this issue on 12.10, or just on 13.04 and later?

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

I can't remember 12.10 too well, but I can confirm that I have experienced the indicator "actually being there" as late as May of this year, in 13.04.

For example, in the attached screen shot, you can see that the indicator was there in May of this year when I was running 13.04.

To the left of the clock you can see an icon of the letter "A". That was what it looked like.

At some point, during the course of running 13.04, it disappeared and has remained gone ever since.

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

Also, I should mention that I've just reinstalled 13.04 (today), and the indicator still does not appear. I've learned to live without it for months; at least my hotkeys work in 13.04.

The reason I reinstalled 13.04 today, is because autokey-gtk doesn't work yet in 13.10 (that upgraded to early today).

I initially upgraded from 13.04 to the alpha of 13.10, and I would have stayed on that alpha had autokey worked.

I waited until today to upgrade from 13.04 to 13.10 again (this time beta), to see if somehow AutoKey was now fixed. But, since it wasn't, I had to reinstall 13.04.

I can't tell you how much I appreciate seeing your activity on these 13.10 bugs. Many thanks!

Revision history for this message
Andrea Azzarone (azzar1) wrote :

Ubuntu 12.10/13.04/13.10 reached end-of-life so it's no longer supported. Can you still reproduce this bug on 14.04 (or laters)?

Changed in unity:
status: New → Incomplete
Changed in autokey (Ubuntu):
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for autokey (Ubuntu) because there has been no activity for 60 days.]

Changed in autokey (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Unity because there has been no activity for 60 days.]

Changed in unity:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.