Comment 6 for bug 474111

Hi,
I also found the above mentioned bug in Archlinux, and found your bug report here. Apparently his bug does not come from the gtk-update-icon-cache command but from something in the icon theme.

Examples:
$ gtk-update-icon-cache -f /home/joyce/.icons/hicolor
gtk-update-icon-cache: Cache file created successfully.

$ gtk-update-icon-cache /home/joyce/.icons/gnome-carbonate/
gtk-update-icon-cache: Cache file created successfully.

$ gtk-update-icon-cache /home/joyce/.icons/LinuxLex-8
gtk-update-icon-cache: The generated cache was invalid.

In the first 2 examples a file has been generated in the root directory of the theme as "icon-theme.cache", but in the case of the third example, where the output says the cache is invalid, the cache file generated in the root directory of the theme had for name ".icon-theme.cache".

The report number 4 shows the message error for hicolor in January 2011 : would have the result been the same if it had been done in the home of the user ? Would it still error out with the latest hicolor version actually available ?

I hope this helps.