After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 698480 - "querying new plugins" runs every startup.
"querying new plugins" runs every startup.
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: Plugins
2.8.2
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-04-21 03:51 UTC by Thomas W
Modified: 2013-07-09 11:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Thomas W 2013-04-21 03:51:52 UTC
I've never changed or installed any plugins. Yet "querying any plugins" runs, taking a long time, every single time I start GIMP.
Comment 1 Michael Natterer 2013-04-21 15:01:43 UTC
Please check if your GIMP directory, and in it the file pluginrc
are writable. This looks like a broken installation to me.
Comment 2 Thomas W 2013-04-22 01:39:36 UTC
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!
Comment 3 Michael Schumacher 2013-05-11 11:58:59 UTC
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?
Comment 4 Thomas W 2013-05-12 01:36:27 UTC
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.
Comment 5 Thomas W 2013-05-12 01:37:13 UTC
And thanks for your interest & assistance, Michael.
Comment 6 Michael Schumacher 2013-05-12 18:28:32 UTC
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.
Comment 7 Thomas W 2013-05-13 01:01:24 UTC
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.
Comment 8 Michael Schumacher 2013-07-09 11:24:00 UTC
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.