I noticed a new trick with the latest Gimp that wasn't there before. I run a Linux system and am forever forgetting to mount the second hard drive before trying to open one of my Gimp files that are stored on that drive. The 8.6 version of Gimp wasn't able to mount the 2nd hdd from within its own open window so I would have to go into my home folder and mount it that way so that Gimp could open the files stored there. With the 8.8 version I can mount the 2nd hdd from within Gimp's open dialogue. Pretty cool.

Thanks for the link paynekj, i gave a try to the different executable and a --verbose

Before in the console after the various parsing, it came to the line
Starting extension : 'extension script-fu'
and then it's where there was this 40 seconds wait before a new line starting by INIT: was added while GIMP interface finally appeared

With the new executable i have the same thing, and before the 40 seconds, (and after the 40 seconds, as usual the INIT: blablabla and the GIMP interface is appearing), i have :

return value 37 from opening C:\Program Files\GIMP 2\share\gimp\2.0\scripts\script-fu.exe
executable : script-fu.exe

nothing else, the "return value 37" is displayed too for the pspi.exe plugin too (if i add the pspi plugin of course) that works from my test
And it's strange to see that it is a different value from what Nfiorentini observe (return value 7)

And unfortunately on my side of the console there's no error, no missing anything, that's puzzling at what is going on then .

I ran the script duplicate script Molly suggested and it shows no duplicate, but it couldn't be the problem as i test with removing all the scripts from the scripts folder to see if there was something there causing problem, but it didn't lowered that odd 40 additional seconds delay (that wasn't existing in Blender 2.8 RC1).

I mentionned no noticable harddrive activity, but i looked at the CPU (i have a dual core) and noticed that during those 40 seconds, one of the 2 CPU have between 60 and 90% load and reach 100% a few times, while the other is getting between 20 and 30%
I know Gimp is multithreaded so the difference of load isn't strange, but the high load of one of the CPU during those 40 seconds despite nothing really happens is odd.

I wonder if it's some of the numerous library constant updates that Gimp is using since RC1 that is playing a role there if one of those updates can be not very good for win32
In 2.8.4 there was a problem with the Partha build on win32 that featured very laggy brush strokes (while "official" 2.8.4 didn't had that), the problem was coming from the cairo library that got an update that wasn't good with win32 (as simply switching the libcairo-2.dll from "official" 2.8.4 and that 2.8.4 from Partha fixed the problem entirely)

Well, the "solution" for me apparently is to go back to 2.8.6. Installing it, then the Liquid Rescale plugin and GIMP Extensions seems to alleviate my errors.

But I don't know why I had no trouble (outside of the slow startup) up until yesterday with 2.8.8. Wish I knew what I broke.

While i remember, at least on the win32 version of "official" 2.8.8 , the file pygimp.env is missing from
...\GIMP 2\lib\gimp\2.0\environ\

And due to that some of the scripts simply do not work or even appear.

I took the pygimp.env from the 2.8.6 win32 version of Partha build i was using and put it in the 2.8.8 and it solved my problem.

So check if despite you're on win64 if you're not running into the same problem, that missing pygimp.env file

FWIW, the 64-bit Windows version of 2.8.6 here ...

http://www.partha.com/

... fires up on my machine in under 6 seconds, even after dropping in 64-bit G'Mic. Of all of the Windows versions GIMP that I've tried thus far (installing, uninstalling through the course of this adventure), this one is the snappiest and smoothest!

GIMP updated to V2.8.8-3 in Fedora 18+

Change Log

Fri Nov 08 2013 GIMP 2.8.8-3
Fix file-bmp: don't close already closed FD

Thu Nov 07 2013 GIMP 2.8.8-2
fix crash in lcms plug-in
fix issues found during static code check

Thanks Tux, Do I use that same terminal command as I did with the last update you posted a week or so ago.
yum --enablerepo=updates-testing update gimp

The update is in the default repos, Molly, so you should get it during your regular update process. To force the matter, you can just run yum update from terminal.

ok thank you... so it is yum update gimp?

You can just run yum update and everything that needs to updated, will be, including GIMP.

You only need to specify the specific app name (like gimp) when installing from the testing repos. That repos is only used for testing purposes and one normally wouldn't install (or update) an app from the testing repos unless they were pretty sure it was OK. I occasionally install apps directly from the testing repos, when I'm pretty sure there are no issues in doing so, as with the recent GIMP update.

What actually happens is that new updates are first pushed to the testing repos. If there are no reports of problems, the updated app is then pushed to the standard update repos, which is where GIMP 2.8.8-3 is currently sitting.

I'm having a similar problem. I DLed and installed gimp 2.8.10 64bit and a first it worked fine, but after installing like 3-4 plugins I started getting this error:

and I am not sure what I did to break it. Heres a list of the few plugins I have installed:

gimp-dds-win64-3.0.1
photo-effects_20
GIMP_Extensions_v2.8_latest
enviromap.scm
layerfx.scm

and that's it, not sure if one of the plugins broke it or what? Though I am also getting this message when I refresh script-fu:



any help you could offer would be appreciated. Also wanted to note that this is a brand new pc, so it has never had any other versions of gimp on it.

Well it seems I fixed my error problems, by deleting the gimp extensions plugin and the photo-effects_20 script. Now it all works fine lol. guess I'll have to find a more solid version of gimp extensions .... anyone know a good place to look for it??

The first error (not found entrypoit g_get_home_dir_utf8) seems to be an error of an older glib-2.0
The current one is delivered with gimp, so I think you have an other, older glib-2.0 anywhere in your path.

For the second error, please open a command window, change to the gimp/bin directory and start gimp with 'gimp-2.8.exe --verbose' (without the " ' "). There maybe it can be seen by an error, why the script could not be loaded.

Well like I said previously, this is a brand new pc, so have never had gimp on it of any kind until now, so I couldn't have an older glib, cause I hadn't installed gimp before now. And deleting the gimp extension plugin got rid of the entry point g_get_home_dir_utf8 error message. So now after deleting the gimp extensions plugin GIMP starts up with no errors.

As for the second error, as I said in last post, deleting the photo-effects_20 script and presets got rid of that error as well. I think that gimp extensions came with a version of the photo-effect script already so it was probably conflicting.

But if anyone knows where I can get gimp extensions app that works with gimp 2.8.10 64bit without giving errors, I would much appreciate it if you could point me in the right direction .

Well I figured out what part of gimp extensions was throwing "the procedure entry point g_get_home_dir_utf8" error message, it was GAP, the animation module, so I uninstalled gimp extensions, then reinstalled but made sure not to check any of the boxes for the GAP, finished installing everything else, and started up gimp. Started up with no error messages yay! And I can still use the rest of the gimp extensions packages, like G'MIC and FX Foundry, etc. Woot!!

Well thank you, that just helped me get through "The Procedure entry point g_get_home_dir_utf8 could not be located in the dynamic link library libglib-2.0-0.dll"

Regards,

Tom C

More than likely you installed a older glib dll file when installing the GIMP extension filter set of GAP. This is why you need to be careful installing anything from a third party other than gimp.org. You probably installed a duplicate scm file also and GIMP saw two as none due to same script name errors.
Try our sister site for extra resources here.
http://www.gimpscripts.com
Also searching here at gimpchat.com can be very helpful when updating to newer plug-ins especially 64 bit.
Also be sure and search for and dispose of OLDER duplicate scm files when installing script files.