gtk-update-icon-cache: The generated cache was invalid.

Bug #474111 reported by Jan Schürmann
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

when doing a gtk-update-icon-cache from terminal, it says: The generated cache was invalid.
i don't know if this is older, but i first realised it after upgrading from jaunty to karmic, because karmic changed my panel icon back and i wanted to change it back to my own.

Revision history for this message
Maciej Warnecki (maciekw5) wrote :

I'm seeing it in Lucid as well. I was trying to change the icon of fusion-icon. It worked before, though.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
Revision history for this message
Jan Schürmann (visionfactory.net) wrote :

it's still here in Maverick!
i see it everytime i do an install or update in the terminal output.

and a "sudo gtk-update-icon-cache -f /usr/share/icons/hicolor" always gives me:

gtk-update-icon-cache: The generated cache was invalid.

1. when updating or installing software at some point it always wants to update the icon cache and then gives the error but that seems to be ignored and the installation normally continues so i haven't let it bother me. until now

2.i expect that updating the icon cache works without any error messages.

3. i always get this error: gtk-update-icon-cache: The generated cache was invalid.
 even if i delete the ".icon-theme.cache" the update icon cache command creates a new file but gives the error mentioned above.

Revision history for this message
Jan Schürmann (visionfactory.net) wrote :

how could i reopen this bug? or is it done by my comment?

Paul Sladen (sladen)
tags: added: gtk-update-icon-cache
Revision history for this message
Mélodie (meets) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.