We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
** Changed in: gnome-panel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/704821 Title: launchers don't expand environment variables Status in “gnome-panel” package in Ubuntu: Expired Bug description: Binary package hint: gnome-panel I had quite a bad user experience today. I've tried to create a simple launcher for Chromium with a command line that included $HOME environment variable [1] and it was not expanded. To my surprise I've found the '$HOME' directory instead spelled with the $ inside. Now I have to use bash -c "command $HOME" command line, but it is not consistent with how would you _as a user_ expect the launcher to behave. As a side note I'd also like to see the flag in launcher properties for executing program in terminal to control console messages. 1. http://code.google.com/p/nativeclient- sdk/wiki/HowTo_RunModules#Step_2:_Launch_the_browser_with_--enable- nacl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/704821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp