"Lock to launcher" fails to spot different application running

Bug #1546042 reported by TimWintle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

I had two installations of an application - one in ~/example1/bin, and one in ~/example2/bin (in the middle of updating versions of this application)

The application in example1 has been locked to the launcher. I removed this launcher with "Unlock from launcher", and then started the application in example2 via a terminal. I right clicked on the icon in the launcher and selected "Lock to launcher".

When I terminated the application, the launcher started the *old* version of the application in example1 - rather than the version which was running when I selected "lock to launcher".

Expected behaviour is that the new version of the application is locked to the launcher.

(Fix was to manually edit the .desktop file in ~/.local/share/applications

Versions:

> lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04

> apt-cache polity unity
Installed: 7.2.6+14.04.20151021-0ubuntu1

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.