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 404691 - libgimp-2.0-0.dll not available
libgimp-2.0-0.dll not available
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: Windows Installer
2.2.x
Other Windows
: Normal major
: 2.4
Assigned To: Jernej Simončič
Jernej Simončič
: 409428 410480 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-05 18:27 UTC by Devon Singer
Modified: 2008-01-15 13:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Devon Singer 2007-02-05 18:27:42 UTC
Please describe the problem:
when ever i start the program and it tries to load all the plug ins it pops up after everyone and says "this application has failed to start because libgimp-2.0-0.dll was not found.  Re-installing the app may fix this problem.  I have reinstalled and downloaded it several times.  I also can not save or open in any file format except gimps file format.  not sure if that is a repercussion of it or not

Steps to reproduce:
1. just by starting the program
2. 
3. 


Actual results:
after it trys to load the plug ins this error pops up after each plug in

Expected results:


Does this happen every time?


Other information:
Comment 1 Devon Singer 2007-02-05 20:08:59 UTC
yes everytime i startup the program it does this the weird thing is that i think i see the file in the program folder but i guess it is not recognizing it?
Comment 2 Raphaël Quinet 2007-02-19 11:36:48 UTC
This is either a duplicate of bug #169824, which was fixed more than a year ago, or this is a problem related to an incorrect installation (e.g. installed as non-admin user and then attempting to run gimp as another user, or running gimp from a different place than from the menu entry created by the installer).  Basically, your PATH is not set up correctly although the installer usually takes care of that.
Comment 3 Raphaël Quinet 2007-02-19 11:39:40 UTC
*** Bug 409428 has been marked as a duplicate of this bug. ***
Comment 4 Raphaël Quinet 2007-02-23 08:39:05 UTC
There are several bugs related to missing dlls, but the reason why this happens is still unclear because the installer usually takes care of setting the right PATH when starting GIMP. In order to help us tracking the source of this problem, it would be nice if the reporter or other users experiencing the same problem could answer the following questions:
- which version of Windows are you using? (including service packs)
- where did you install GIMP? (please specify the exact path)
- did you install GIMP as administrator or as a restricted user?
- did you run GIMP as administrator or as a restricted user?
- did you have a previous version of GIMP installed on your system?
- in particular, did you have any 2.0.x or 2.2.x version?
- when you reinstalled GIMP, did you uninstall the previous version first?
- was/is the previous version installed in the same location? (if not, please specify the previous installation path)
- did you do anything special when installing or uninstalling gimp, like changing some options, moving files around, etc.?
- did you compare several ways to start GIMP (desktop icon, menu, direct click on the program in the installation folder) and do you always get the same errors?
Comment 5 contact 2007-03-06 10:06:18 UTC
I just installed GTK+ 2.10.6-1, and then GIMP Win32 2.3.14-i568, from sf.net/projects/gimp-win; no plugin loaded because the following DLLs could not be found:

- libgimp-2.0-0.dll
- libgimpui-2.0-0.dll

After adding {PROGRAMS}\GIMP-2.0\bin to %PATH% (which was not added by the installer!), GIMP worked well.

So I recommend checking the installer scripts if they are complete, logical, and checking for the unexpected.
Comment 6 Raphaël Quinet 2007-03-06 10:30:03 UTC
(In reply to comment #5)
> After adding {PROGRAMS}\GIMP-2.0\bin to %PATH% (which was not added by the
> installer!), GIMP worked well.
> 
> So I recommend checking the installer scripts if they are complete, logical,
> and checking for the unexpected.

In order to do that, we have to know what was unexpected.  Could you answer the questions in comment #4?  You have already answered some of them, but please provide precise answers for all other questions.  Maybe one of these answers would help us to understand what is different about your system and why the installer did not do what it is expected to do.
Comment 7 contact 2007-03-06 10:47:08 UTC
- Windows XP Professional, german, SP2, constantly updating
- E:\Programme\GIMP-2.0
- installed as administrative user
- started as administrative user
- installed this system a few weeks ago, fresh installation of a GIMP
- first installed GTK+ 2.10.6-1; set it up to german locales; afterwards, installed GIMP Win32 2.3.14-i568 (still with enabled GTK+ option)
- only started it from the installer generated desktop link
Comment 8 contact 2007-03-06 10:58:07 UTC
P.S.:

I did not reboot after installing the packages. And according to the "Working place" environment dialog, and the "set" command in the command line interpreter, the %PATH% contained "E:\Programme\Gemeinsame Dateien\GTK\2.0\bin"
("Gemeinsame Dateien" ~ "Common Files"), but not "E:\Programme\GIMP-2.0\bin". And without including them to the PATH, the plugins didn't find the DLLs.

Is there any other technology used in the plugins to locate the common libraries? Should they look for registry settings or special environment variables? Please request specifically if I can tell you more details.
Comment 9 Raphaël Quinet 2007-03-06 12:37:25 UTC
Thanks for this additional information.  It is very useful to know that your installation was on a "clean" system and that the path was updated for GTK+ but not for GIMP.  I will let Jernej ask other questions if necessary. :-)
Comment 10 Michael Schumacher 2007-03-06 12:39:59 UTC
Hm, this report covers two different versions of GIMP - which do use different approaches to set PATH (2.2: App Paths entry in the registry, 2.3: default.env file).

The reason for the latter has been identified - it should be "Path" instead of "PATH" in the default.env file. Please try to change this and report back.

Problems in 2.2 are usually caused by not installing with admin rights (and thus not having the App Paths entry).
Comment 11 Michael Schumacher 2007-03-16 14:17:04 UTC
Setting to NEEDINFO; should have done so when adding comment #10 already.
Comment 12 Michael Schumacher 2007-03-16 14:23:49 UTC
*** Bug 410480 has been marked as a duplicate of this bug. ***
Comment 13 Michael Schumacher 2007-03-24 13:22:31 UTC
This has to be sorted out for the 2.4 installer (or preferably for one of the next 2.3s already).
Comment 14 Jonatas Miguel 2007-04-30 13:30:05 UTC
As far as I know all you have to do is change the "Start in" parameter for the gimp shortcut to: "C:\Program Files\GIMP-2.0\bin\" and your problem will be fixed. Though I'm pretty sure that this is a problem with how the shortcut is being created with the windows installer script...

B.T.W.

Both the desktop and start menu shortcuts have the same problem so don't forget to change both of them...

I hope this helps!
Comment 15 Jonatas Miguel 2007-04-30 13:52:46 UTC
Just for good measure, I added "C:\Program Files\GIMP-2.0\bin\" to my environment variables and tried changing the "Start in" parameter of the shortcut to something else completely (I set it to C:\) just to see if that would resolve the problem instead of having to change the shortcut "Start in" parameter to the path that I stated in my last post and it gave me the missing dll error anyway. The path that is set by default by the installer is: "%USERPROFILE%\My Documents\My Pictures"
Comment 16 Michael Schumacher 2007-05-01 12:37:50 UTC
The "Start in" parameter is set correctly - or at least to a reasonable default. Changing it is a workaround, the solution would be to find out why the registry entry (assuming 2.2 here, as the 2.3 problem is solved; see comment #10) is not set.
Comment 17 123tomek 2007-05-23 21:53:41 UTC
I have the same problem. I have 

- Windows XP Professional, polish, SP2, constantly updating
- C:\Program Files\GIMP-2.0
- installed as administrative user
- started as administrative user
- installed this system a one day ago, fresh installation of a GIMP
- first installed GTK+ 2.10.6-1; set it up to polish locales; afterwards,
installed GIMP Win32 2.3.14-i568 (still with enabled GTK+ option)
- only started it from the installer generated desktop link and quickstart link


1. If I add to the PATH C:\Program Files\GIMP-2.0\bin   ( with cmd command: PATH=C:\Program Files\GIMP-2.0\bin;%PATH%) problem is not solwed.
2. If I delete all from default.env and put inside PATH=C:\Program Files\GIMP-2.0\bin problem is not solwed
3. If I copy all dll from C:\Program Files\GIMP-2.0\bin to the C:\Program Files\Common Files\GTK\2.0\bin problem is solwed - was OK but I delete this dlls and try other steep:
4. When I change the "Start in" parameter for the gimp shortcut to: "C:\Program Files\GIMP-2.0\bin\" (Comment 14 Jonatas Miguel) was OK too.

Comment 18 Michael Schumacher 2007-05-30 10:12:07 UTC
If you typed PATH and not Path, it's not surprising that editing default.env didn't work.


BTW, in my opinion this bug is solved. Should we keep it open until an installer with a correct default.env is released or closed it now? 

Jernej, couldn't you just release an updated installer with this change, even if you're still unable to provide newer builds?
Comment 19 Catherine 2007-06-25 11:14:10 UTC
Sorry to ask what may now be a stupid quesion. I have spent hours on this bug now!

I have installed GTK +2 runtime environment, then Gimp for Windows version 2.2.15. It says it can't find a large number of dll's when I try to launch. (I am an administrator on the computer. I have Windows XP Home Edition.)

I went into File -> Preferences -> Folders -> Environment and added the path (C\:Program Files\Gimp-2.0\bin) there by clicking on browse - '...', but it still says it can't find them when I relaunch.

Where is everyone typing 'Path' not 'PATH'?

When I downloaded Gimp onto another machine a year ago it worked perfectly. Is there any way of getting the version that was around then?

Thank you very much!

Catherine
Comment 20 Michael Schumacher 2007-06-25 12:52:21 UTC
I'd vote for closing this bug now. It has become too confusing to be helpful, and the Path <-> PATH problem is OBSOLETE in current 2.3 (IIRC there have been changes to glib). 

The problem with 2.2 is usually caused by installation problems. we do not handle these in Bugzilla (unless they are installer bugs), please do ask for advuice on the gimpwin-users mailing list.