Bug Description

What happens: running a Python application, such as Kabikaboo gives a Unity launcher entry. Right clicking this entry and selecting "keep in launcher" keeps the item in the launcher as expected. However, when the application has been closed, clicking this launcher entry will not restart the program. Furthermore, these launcher entries do not seem to persist after logout/login.

-------------------------
Desired Resolution:

- Applications that are "kept in launcher" should persist between sessions and clicking the icon should launch the application, even if they do not have a .desktop file.

I installed Kabikaboo launched it from applications places and pinned it to the launcher and closed the app, then starting from it launcher worked fine. after that removed it from the launcher and started Kabikaboo from terminal and clicked on 'keep in launcher' and closed. But this time it won't start.

summary:

- Python applications do not work correctly in Unity launcher+ Python apps launched from terminal cannot be launched after pinning to+ launcher

The only way to fix this bug (and many others, not strictly related to python, I guess) would be to support something that unity really would need: when an app that has no related .desktop file is in the launcher and the "Keep in launcher" menu item has been selected, unity should generate a .desktop file for it (properly filled with all the retrievable fields, including StartupWMClass) in ~/.local/share/applications/unity.

It's not that hard, but the fact is: which is the component that should do it? I'd say no to BAMF, making this directly in unity but this would need to double the implementation in unity-2d... So, when this doubt is solved, the implementation will follow ;)

- Apps launched from terminal or without a .desktop file cannot be- launched after pinning to launcher+ Launcher - Apps launched from terminal or without a .desktop file cannot+ be launched after pinning to launcher

[ Marco Trevisan (Treviño) ]
* BamfControl: add an API to allow generation of local .desktop file
for a BamfApplication. Add a bamf_control dbus method that requests
to generate a new local .desktop file for the provided application
path. In case the application has alredy a desktop file, the request
is ignored. Otherwise we use some euristic to generate an hopefully
valid file saved in $XDG_DATA_HOME dir. Also added a new
DesktopUpdated signal to the BamfApplication DBus interface that is
emitted when the .desktop file for an application is set (for now).
(LP: #753305)

[ Marco Trevisan (Treviño) ]
* ApplicationLauncherIcon: Create a local desktop file when sticking
an app that has not Also make icon sticky only if both the icon
itself and the inner app is sticky as well. (LP: #1209320, #753305,
#765466, #754334, #704046)