Bugzilla – Bug 551709
Emacs has missing icons on a minimal install. Fixed after manually running SuSEconfig
Last modified: 2010-04-06 15:14:47 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.4) Gecko/20091028 Iceweasel/3.5.4 (Debian-3.5.4-1) Minimal server install from NET Build331 Emacs installed using zypper. icons missing and emacs:12191): Gtk-WARNING **: Error loading theme icon 'gtk-open' for stock: Unrecognised image file format (emacs:12191): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory Reproducible: Always Steps to Reproduce: 1. Install emacs after minimal install 2. DISPLAY=remote:0 emacs Actual Results: icons missing and emacs:12191): Gtk-WARNING **: Error loading theme icon 'gtk-open' for stock: Unrecognised image file format (emacs:12191): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory appears a *lot* Expected Results: icons appear and no error messages running "SuSEconfig" manually fixed this.
About which emacs are you talking? XEamcs or GNU Emacs?
IMHO this is a GNOME problem as the error message is from a gnome interface. The GNU Emacs has its pixmap installed under /usr/share/pixmaps/ as emacs.png and several icons under /usr/share/icons/hicolor/. If GNOME requires to run SuSEconfig to find the icons this should (IMHO) done before starting GNOME.
Hi Werner This is GNU emacs and I'm pretty sure this is not a gnome problem - I'm not running gnome at all. It's not even installed. I'm running a minimal install, server only, and displaying emacs via a remote DISPLAY. Nb, the icons in question are the icons inside emacs on the menu bar; not desktop icons (this may not have been clear).
On running GNOME I meant also the library its self. It seems to me that libgdk is not able to find common icons without running SuSEconfig. This is a bit strange as emacs installs all required icons and I expect that a library should find them, shouldn't it? Or does this mean that every package using GtK/GdK has to run SuSEconfig out from the spec file? Vincent? As you have the majority in the changes of GtK2 I ask you about this behaviour. Does SuSEconfig have to be called by every package providing icons at /usr/share/icons?
The short story is that all packages installing icons in a theme directory should call gtk-update-icon-cache. But the thing is that we don't want every rpm to trigger this when you install tons of packages, and so we'd want triggers. See bug 365649 for the discussion and https://features.opensuse.org/305472 for the resulting feature request. The likely fix will be file triggers (see http://stick.gk2.sk/blog/2009/10/rpm-summit-at-the-opensuse-conference-2009/) So, going back to this bug: either the package should call gtk-update-icon-cache, or call SuSEconfig, or wait for a proper fix for the whole issue.
.. now ... what's about this proper fix for gtk-update-icon-cache problem?
(In reply to comment #6) > .. now ... what's about this proper fix for gtk-update-icon-cache problem? As I said in the previous comment, we're waiting for a feature in rpm. Until it's there, the only fix is to call gtk-update-icon-cache in the scriptlets of the emacs package
Let's make this a duplicate of bug #305472 as this is a duplicate and the way of using gtk-update-icon-cache seems to be a nogo, compare with bug #395056 *** This bug has been marked as a duplicate of bug 365649 ***