Another alternative, if you want to dig further, is to use Process
Run that, filter on "gimp", and look at what it accesses during
startup. Somewhere in that last is a) a file it reads that is
corrupt, or b) a file that's missing. Either way, you'll see exactly
what files gimp touches on startup, and there might be some surprises
I've used that before to find startup problems with programs accessing
files in places I did not suspect. Very useful.
gimp-user-list mailing list