GNOME Bugzilla – Bug 698480
"querying new plugins" runs every startup.
Last modified: 2013-07-09 11:24:00 UTC
I've never changed or installed any plugins. Yet "querying any plugins" runs, taking a long time, every single time I start GIMP.
Please check if your GIMP directory, and in it the file pluginrc are writable. This looks like a broken installation to me.
Thanks Michael. I spent a while searching the GIMP install & executable directory.. nothing.. but I don't think that was where you meant. Searching later, I found the "pluginrc" file in C:\Users\Tom\.gimp-2.8. It's present, appears fine & is timestamped yesterday (from when I last ran GIMP). When I run it today, "Querying new plugins" comes up -- but only briefly for 1 plugin, pyconsole.py. Perhaps it coming up for an extended time yesterday, was connected with their having been a DST (daylight savings time) transition since I last ran it??? Seems to me I've seen "querying new plugins" before, but perhaps it's not very long all the time. However GIMP startups typically aren't "fast" when I use it -- typically on different days. Three test startups today, while writing this response, seemed a lot faster than my usual experience -- but I can't distinguish how much of this is caused by files from disk having been cached by the OS. Thanks for your prompt response!
DST changes cuase this, yes. And the pyconsole.py one is expected as well. So, did I get this right, and the whole issue has only happened once?
Thanks Michael, I think we've confirmed the full, very slow, "querying plugins" only happened once after the DST change. 'Querying plugins' appears for Python every startup. That, & general waiting every time I start GIMP, gave me the impression this was an issue every time. So this is partly mis-reported -- but GIMP startup could always be faster, and full re-query on DST is less than desirable.
And thanks for your interest & assistance, Michael.
For me, starting GIMP takes about 15 seconds on an outdated 1.6 GHz single-core system. Most of that seems to be spent on starting the Script-Fu extension. Optimizing this is handled in bug 374854. There's also bug 330099 about lazy loading of data files.
Yes, I get about 11 seconds even with a quad-core Core2 at 2.66 GHz. 'py-console.py' and especially Script-Fu take a lok of the time.
Because I'm seeing some pointers to this bug from articles about the 2.8.6 32 bit issue: that one is handled in bug #703113. Let's close this one, as this was a different known issue.