* HammerBob [11-09-13 11:44]:

After I upgraded from GIMP 2.8.6 to 2.8.8 on my Windows 7 x64 computer I get this error message when I try to open a JPEG file as a new layer:

ufraw-gimp.exe - Entry Point Not Found The procedure entry point g_get_home_dir_utf8 could not be located in the dynamic link library libglib-2.0-0.dll.

A Google search turned this up: https://bugzilla.redhat.com/show_bug.cgi?id=951588

When I upgraded I used the distribution from here: http://www.gimpusers.com/downloads/95-gimp-2-8-8-windows

How can I fix this?

There was more discussion about this for windows. You need to search further for "windows" solution. I do not run windows and do not recall the exact solution, something about the *location* of the dll, iirc.

(paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri
http://en.opensuse.org    openSUSE Community Member    facebook/ptilopteri
http://wahoo.no-ip.org        Photo Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535                    @ http://linuxcounter.net

On 09.11.2013 17:43, HammerBob wrote:

After I upgraded from GIMP 2.8.6 to 2.8.8 on my Windows 7 x64 computer I get this error message when I try to open a JPEG file as a new layer:

ufraw-gimp.exe - Entry Point Not Found The procedure entry point g_get_home_dir_utf8 could not be located in the dynamic link library libglib-2.0-0.dll.

That could be the following change in the glib library: https://mail.gnome.org/archives/commits-list/2013-February/msg07050.html

Short summary:

The change hides some API that should never have been exposed on 64 bit platforms, but was by accident. Applications are expected to use g_get_home_dir in their code, which might be linked to g_get_home_dir_utf8 via #defines depending on the platform (afaik this happens for 32 bit windows platforms).

Someone should recompile the third-party ufraw plug-in with a recent glib.

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD

Someone should recompile the third-party ufraw plug-in with a recent glib.

As I have the same problem, I wonder why Gimp 2.8.8 does call ufraw anyway for opening a .jpg? Gimp 2.8.6 opened any image file apart from raw data without ufraw even beeing on my harddisk. And as far as I get, ufraw development seems to have ceased.

As I have the same problem, I wonder why Gimp 2.8.8 does call ufraw anyway for opening a .jpg? Gimp 2.8.6 opened any image file apart from raw data without ufraw even beeing on my harddisk. And as far as I get, ufraw development seems to have ceased.

I'm not posting this long after the last poster, but I found this page when I searched on the same problem, after installing GIMP 2.8.14. I tried re-installing GIMP itself, and that didn't help. What DID help was uninstalling and then re-installing the extensions package. I don't know why it worked, but it worked! Just figured I'd post in case someone else came across this page looking for an answer to the same problem...