The bug seems to have been fixed already, still, if you are interested:
The exact steps can be found to the forum thread linked in the original report. For brevity, here's a quotation:
---
I dragged a copy of the terminal icon (gnome-terminal) from the Applications menu, onto the panel at the top. I am using it to open an ssh session to another computer automatically with
gnome-terminal -e "ssh -Y etc...
and that works, but I wanted to rename it. I change it's name and comment in properties, but it just keeps reverting back to the original name and comment. I have other launch icons on the panel, like one for Thunderbird email client, and those can be renamed.
---
Additionally, I also tired to create a fresh launcher (from the scratch) but the name would not change either.
I assume at that date I was using ubuntu feisty 64bit already (otherwise ubuntu edgy 32). I don't know about other users reporting the bug. However, I tried now to repeat the behaviour described, and I couldn't replicate it anymore. I assume it might have been fixed by some upgrades between the bug report and now.
The bug seems to have been fixed already, still, if you are interested:
The exact steps can be found to the forum thread linked in the original report. For brevity, here's a quotation:
---
I dragged a copy of the terminal icon (gnome-terminal) from the Applications menu, onto the panel at the top. I am using it to open an ssh session to another computer automatically with
gnome-terminal -e "ssh -Y etc...
and that works, but I wanted to rename it. I change it's name and comment in properties, but it just keeps reverting back to the original name and comment. I have other launch icons on the panel, like one for Thunderbird email client, and those can be renamed.
---
Additionally, I also tired to create a fresh launcher (from the scratch) but the name would not change either.
I assume at that date I was using ubuntu feisty 64bit already (otherwise ubuntu edgy 32). I don't know about other users reporting the bug. However, I tried now to repeat the behaviour described, and I couldn't replicate it anymore. I assume it might have been fixed by some upgrades between the bug report and now.