Some apps (KeePassX and ClipGrab) don't show in the launcher when opened

[Nicolás Abel Carbone]

Some apps, like KeePassX and ClipGrab, doesn't show a launcher icon when opened.

When I open one of this apps, the launcher icon appears briefly, and then disappears. I attach a video showing the problem.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.12-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Tue May 22 10:11:03 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

[Nicolás Abel Carbone (nicocarbone)]

Some more info about this bug. I could reproduce it in several PCs.

In the case of ClipGrab (which was installed from its ppa: ppa:clipgrab-team/ppa) sometimes, it has to be opened several times in order to see the bug. When the bug is not present, it shows two icons in the launcher briefly, and then one of the disappears, leaving only one.

For KeePassX, the bug is only present when the program is trying to open a database on startup. It asks for the password, and the it closes the password dialog and opens the main window. The icon disappears when the password dialog closes and does not reappear when the main window opens. If there is no database to open, and no password dialog appears at start, the bug is not present.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nicolás Abel Carbone (nicocarbone)]

This bug appears to be solved with the proposed updates to bamfdaemon and libbamf (0.2.118-0ubuntu0.1) and/or unity 5.12-0ubuntu1.1 .

[Sebastien Bacher (seb128)]

thanks, closing the bug then!

[Daniel van Vugt (vanvugt)]

If this bug is now fixed, then it would have been fixed by this fix --> bug 995916.