Red Hat Bugzilla – Bug 121929
crystal icons for k-menu are missing
Last modified: 2007-11-30 17:10:41 EST
Description of problem:
After the upgrade from FC1 to FC2 I noted that the crystal
icons in my k-menu (for Accessories/Graphics/...) are
missing (they are replaced by some gnome icons). This
looks really ugly! Please fix.
Version-Release number of selected component (if applicable):
Still here with kdebase-3.2.2-4 and kdelibs-3.2.2-6
i'm still working on it ;-)
I just looked at the differences between FC1 and FC2
KDE in FC1 (kdebase-3.2.2-0.1) does not use the redhat menues,
it uses the KDE-*.directory files.
KDE in FC2 uses the redhat *.directory files (and not the
kde-*.directory) files. Moreover, since the Redhat-*.icons
are not present in the crystal icon set, it uses those from
hicolor. Hoever, the new gnome-icon-theme installs everything into
/usr/share/icons/hicolor (rather than /usr/share/icons/gnome) and
hence kde picks those.
Still present in fc3 kde 3.3.1
This is a somewhat more fundamental problem with fedora/rh settings in kde.
Since the KDE menu is built from /etc/xdg/menus and there are no corresponding
icons at all in crystal for the Icon=redhat-* entries, they are, as Gerald
pointed out, substituted from bluecurve(?). The solution (which i will
implement ASAP) is to symlink the appropriate crystal package_ icons into
redhat- icons, so kiconloader can find those versions.
yes, symlinking the appropriate crystal package icons into redhat icons
is a just a workaround. I think, a clean solution would be that we have to define
a common icon name for that or perhaps overtake the icon name from KDE.
Then changing the item "Icon=..." in all the desktop files in
/usr/share/desktop-directories/, add symlinks in bluecurve icons theme
Ok, i looked into the issue some more. In bluecurve, the redhat-*.png icons are
just symlinks to real icons as well, so adding similar symlinks to crystal
shouldn't be a problem, really. What however is more of a problem is to find
corresponding icons in crystal... Going to do so now.
Should be fixed. Please report omissions in a new bugreport if you still find