This bug was fixed in the package upstart-app-launch - 0.3+14.04.20140213-0ubuntu1
--------------- upstart-app-launch (0.3+14.04.20140213-0ubuntu1) trusty; urgency=low [ Ted Gould ] * Unregister for Unity's Resume signal * Function to get the log file for the application * Add GIR support to libual * Remove an invalid substitution that we weren't using (LP: #1220591) -- Ubuntu daily release <[email protected]> Thu, 13 Feb 2014 13:14:51 +0000 ** Changed in: upstart-app-launch (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Unity API bugs, which is subscribed to Upstart Application Launcher. https://bugs.launchpad.net/bugs/1220591 Title: click hook tries to use ${id} in Exec Status in Upstart Application Launcher: New Status in “upstart-app-launch” package in Ubuntu: Fix Released Bug description: upstart-app-launch's click hook tries to use the app ID in Exec, passing it as ${id}. However, ${id} is not substituted in Exec. As it turns out, desktop-hook doesn't actually use this; indeed it exits with an error if it's passed any arguments. You get away with this because Exec is passed through the shell and the shell expands ${id} to the empty string; but you shouldn't rely on this. === modified file 'upstart-app-launch-desktop.click-hook.in' --- upstart-app-launch-desktop.click-hook.in 2013-08-07 01:55:31 +0000 +++ upstart-app-launch-desktop.click-hook.in 2013-09-04 08:52:33 +0000 @@ -1,4 +1,4 @@ Pattern: ${home}/.cache/upstart-app-launch/desktop/${id}.desktop -Exec: @pkglibexecdir@/desktop-hook ${id} +Exec: @pkglibexecdir@/desktop-hook User-Level: yes Hook-Name: desktop To manage notifications about this bug go to: https://bugs.launchpad.net/upstart-app-launch/+bug/1220591/+subscriptions -- Mailing list: https://launchpad.net/~unity-api-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~unity-api-bugs More help : https://help.launchpad.net/ListHelp
