Bugzilla Bug 92289

I recently upgraded to gnome 2.10 on my ~x86 box.  I removed the "Menu Bar"
from my panel and added a "Main Menu" object instead (i.e., the small icon
rather than the strip of menus).

Now when I log into gnome, I get an error dialog which says "Failed to load
image gnome-main-menu" "Details: Icon not found".  The icon is then the brown
no-icon-found default image instead of the black/cyan gnome foot.

Is this something I've done or can someone else confirm this error?

temporary fix:
The directions here told me which gconf key to edit to change to a custom icon:
http://gnome-look.org/content/show.php?content=22413
Setting the custom icon to gnome-logo-icon-transparent.png works fine.

Exactly the same issue for a non root user.
root is ok.

This problem is very strange. What version of gnome-panel do you have in your
system?

Can you verify the location and permissions of gnome-main-menu.png? (it should
be under /usr/share/icons/hicolor/48x48/apps)

I get the same error message here after just upgrading to gnome-2.10
(gnome-base/gnome-panel-2.10.0).

brix@sponge ~ $ find /usr/share/icons/ -name gnome-main-menu.png -exec ls -l {} \;
-rw-r--r--  1 root root 2314 Jun  6 10:12
/usr/share/icons/HighContrastLargePrint/48x48/apps/gnome-main-menu.png
-rw-r--r--  1 root root 3090 Jun  6 13:05
/usr/share/icons/hicolor/48x48/apps/gnome-main-menu.png
-rw-r--r--  1 root root 1992 Jun  6 10:12
/usr/share/icons/LowContrastLargePrint/48x48/apps/gnome-main-menu.png
-rw-r--r--  1 root root 2369 Jun  6 10:12
/usr/share/icons/HighContrastLargePrintInverse/48x48/apps/gnome-main-menu.png

What is the value of the gconf key /desktop/gnome/interface/icon_theme in your
system? (you can check this doing e.g. "gconftool-2 -g
/desktop/gnome/interface/icon_theme")

Also, please try starting gnome-session from a terminal and paste here the
output that it sends to stdout/stderr.

comment #2:  I have gnome-panel 2.10.0 and the icon you asked about is in the 
path you described.

comment #4:  That command returns "gnome".  I'm pretty sure I tested it using 
the default theme before and still had the missing icon.  Haven't tried gnome-
session business.  Will try it if I get a chance.  (I'm currently travelling so 
I may not be very responsive to requests for information.)

Hi,
My gconf key says "crux"

My gnome-session error output is 4.7K, so I'll add it as an attachment.
Std out was short and boring.

Created an attachment (id=60754) [details]
Output from gnome-session, as done from an xterm

Created an attachment (id=60756) [details]
Output of `gnome-session`

brix@sponge ~ $ gconftool-2 -g /desktop/gnome/interface/icon_theme
gnome

The gnome-main-menu.png image loads fine in an image viewer, so it is not
corrupt.

I experience the same problem. Copying
/usr/share/icons/hicolor/48x48/apps/gnome-main-menu.png to /usr/share/pixmaps
removes the symptom.

Please don't use workarounds as copying the image to /usr/share/pixmaps while
we
debug the problem.

Let's try one more thing before moving to trickier things. Run the following
command as root:

  gtk-update-icon-cache -f /usr/share/icons/hicolor

And tell us if it changes anything. Thanks.

That solution has worked for me. I can now create a main menu without errors.

It works for me too!
Great!

It said "cache created successfully"

seems to work for me.

`gtk-update-icon-cache -f /usr/share/icons/hicolor` fixed the problem here as
well.

The fix is now part of gnome-panel's ebuild. Thank you all for your help.

That is fixing of symptoms. I think I asked not to cache hicolor yet just
because of these reasons, but i guess it didn't get picked up.

I didn't know about foser's plans for handling icon updates, but from what I
understand the idea was handling it in gnome2.eclass. For this reason, I've
added the function gnome2_icon_cache_update() to the eclass; it's called from
gnome2_pkg_post{inst,rm}, so we can start removing any piece of code that calls
gtk-update-icon-cache manually from the ebuilds now.

If there is any feedback regarding this new function, I suggest we discuss it in
another bug, we've abused this one enough :).