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 782537 - Three entry point errors on Gimp startup.
Three entry point errors on Gimp startup.
Status: RESOLVED DUPLICATE of bug 756922
Product: GIMP
Classification: Other
Component: General
2.8.22
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2017-05-11 21:56 UTC by Gregory Ross
Modified: 2017-06-19 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Three errors when starting Gimp 2.8.22 (160.17 KB, image/jpeg)
2017-05-11 21:56 UTC, Gregory Ross
Details

Description Gregory Ross 2017-05-11 21:56:38 UTC
Created attachment 351672 [details]
Three errors when starting Gimp 2.8.22

When starting Gimp, there are three Entry Point errors (_ZdlPvy) that pop up. Gimp doesn't continue starting until the 'OK' button is clicked. I do not know of any effects they have while Gimp is running. I am including a picture of all three errors.
Comment 1 Michael Schumacher 2017-05-11 22:02:32 UTC
Worked fine for me. Might be an instance of DLL hell on your system - maybe this DLL was brought by a third-party plug-in.
Comment 2 Michael Schumacher 2017-05-12 12:18:54 UTC
A possible approach to investigate this on your system:

1. Get Process Monitor: https://en.wikipedia.org/wiki/Process_Monitor
2. Use it to create a log when starting GIMP. 

Among other things, this tool shows all files accessed by processes on your system. Filters allow to limit the data shown, the DLL file name would be a suitable filter value.

This will allow you to see where the DLL file with the missing entry points is located.


3. Figure out why this DLL file is there

It should have (and does) come with the GIMP Windows installer in a suitable version, but might have been replaced by any other installer or yourself, e.-g. when installing a third-party plug-in. Or it might simply by lying around on your system, which is searched before the one the GIMP installer brought (this mess is what is called DLL hell).

4. Return with your findings, preferably before you do something. If you want to attach a Process Monitor log, make sure you do so in plain text.
Comment 3 Michael Schumacher 2017-06-19 14:33:57 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 756922 ***