Background:
There is a new application XXX, which is distributed as a zip-file.
I created a directory ~/programs/XXX
, stored the zip-file in it and unzipped it. Now I got a directory ~/programs/XXX/XXXv.1
and in it program xxx and others.
I made xxx executable, dubble-clicked it in the file manager. A new icon appeared in launcher and program xxx started. After quitting the program the icon stayed in launcher. I was able to restart the program from the icon.
After a few days a new version of app xxx was distributed, got the zip, unzipped,got directory ~/programs/XXX/XXXv.1.1
, in it program xxx and others.
I deleted the icon from the launcher (to programm xxx v.1), started ~/programs/XXX/XXXv.1.1/xxx
from file manager, the icon appeared again in the launcher, the new version of started. After quitting the program and relaunching from the icon in launcher I noticed that the newly created icon started the old version of the program, despite the icon being created by the launch of program xxx from the new version directory.
Question:
How to make the launcher icon point to the program in the new version directory, from where the icon was created from?
Further investigation:
After renaming the program name in the old version directory the newly created icon could not launch the program. So in fact the newly created icon from the newer version of the program points to the old version of the program.
There must be a hidden config file with a pointer to the old executable, which is not deleted, when the icon to the old version is deleted.
When the new version of the program is started,an icon for the new version is created, new version of the program is started, but when restarting from the icon, old version of program is started.
What is that hidden config file of the launcher icon and how to change the program file it points to?