For me the next entry is:
Strangely, same checksum...
Three more ideas:
- As Rich says, this could be a problem with clipboard contents when the tag cache file is created. Experiment wiht varoius things (copy a small image to the clipboard)
- The two brushes in the tag file seem to come from what is in Linux the file /usr/share/gimp/2.0/tags/gimp-tags-default.xml
I don't quite understand the purpose of this file but given the presence of various foreign language indications, I wonder if this could be a problem with some system language setup?
- If I rename my tags.xml and run Gimp with --verbose I see it complain about not finding the tag cache, but there is no message about updating it. It is eventually created when Gimp exits. So it would be worth erasing/renaming it and see what happens when it is not there when Gimp starts.
After that, if nothing works, head to http://bugzilla.gnome.org and file a bug. The developers will come to the rescue. Hmm. Looks like this bug has been reported (always on Windows 7...). See https://bugzilla.gnome.org/show_bug.cgi?id=704816
Code:
<resource identifier="gimp-brush-clipboard" checksum="157dcef48665ab465439cfaf10d6feeb">
<tag>hearts_gimp_brushes_by_hawksmont</tag>
</resource>Strangely, same checksum...
Three more ideas:
- As Rich says, this could be a problem with clipboard contents when the tag cache file is created. Experiment wiht varoius things (copy a small image to the clipboard)
- The two brushes in the tag file seem to come from what is in Linux the file /usr/share/gimp/2.0/tags/gimp-tags-default.xml
I don't quite understand the purpose of this file but given the presence of various foreign language indications, I wonder if this could be a problem with some system language setup?
- If I rename my tags.xml and run Gimp with --verbose I see it complain about not finding the tag cache, but there is no message about updating it. It is eventually created when Gimp exits. So it would be worth erasing/renaming it and see what happens when it is not there when Gimp starts.
After that, if nothing works, head to http://bugzilla.gnome.org and file a bug. The developers will come to the rescue. Hmm. Looks like this bug has been reported (always on Windows 7...). See https://bugzilla.gnome.org/show_bug.cgi?id=704816