After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 488944 - missing default icon for icon-less launchers
missing default icon for icon-less launchers
Status: RESOLVED DUPLICATE of bug 435150
Product: gnome-panel
Classification: Other
Component: panel
2.18.x
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-22 10:17 UTC by James F. Carter
Modified: 2007-11-13 07:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description James F. Carter 2007-10-22 10:17:42 UTC
Please describe the problem:
adding a launcher to a panel without specifying an icon results in an invisible launcher. ~/.gnome2/panel2.d/default/launchers has an appropriate .desktop file, and editing that file so that it does have an icon causes it to appear on the panel.

Steps to reproduce:
1. right click on panel, select "add to panel".
2. select "custom application launcher"
3. enter a name "test" and a command "test", but don't specify an icon
4. click OK


Actual results:
no launcher appears in the panel, although the following is written to ~/.gnome2/panel2.d/default/launchers/test.desktop:

[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Terminal=false
Name[en_GB]=test
Exec=test
Name=test


subsequently appending "Icon=gnome-unknown.png" to this file causes the launcher to appear - so the correct icon does exist.

Expected results:
the launcher should appear with the default icon "gnome-unknown".

Does this happen every time?
yes.

Other information:
Comment 1 Vincent Untz 2007-11-13 07:03:04 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 435150 ***