Description of problem:
Icon reference in .desktop file contains file extension (.png) which prevents
effectively theming it, e.g. if the used icon theme is based solely on SVGs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Hard link on .desktop file
name convention should follow Icon Naming Guidelines.
Just dropping the extension is fine (i.e. to Icon=system-config-boot), but
would be even better if the icon name could be changed to something more
general and follow the Icon Naming Guidelines . Suggestion is
Also, as the icon is used in the application itself, it would be nice to look
it up the correct way . GTK has already prepared look-up functions for that,
so the implementation should not be hard. Patch attached to bug #454402 might
this bug has been fixed in Fedora 10.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Hm... as petrosyan noted, this is already fixed. I wonder, why the bug is still open... Closing as nextrelease.