No. The name is still libgtk-win32-2.0.0.dll, but it can be a 64bit version.
Jernej Simoncic used the newest libraries, that were available, when building the windows installer.
It is not gimps fault, it is the fault of the 3rd party libraries, so I think, Jernej Simoncic will create a new
installer soon. In the meanttime, exchange
libgtk-win32-2.0.0.dll
libcairo-2.dll
libpixman-1-0.dll
with the versions from gimp-2.8.10 or use parthas build, if it is out.

So if I understand this correctly, 2.8.12 was broken for everybody and got an immediate fix, whereas 2.8.14 is broken for Windows and still available. Which means unsuspecting beginners are downloading a version of GIMP that has a more difficult user interface than usual. Just what we needed.

When I tell people I use GIMP, more often than not they respond with something like, "why don't you get grownup software like Photoshop?" I try to keep up the good fight... but... but... I mean, shouldn't the broken Windows builds for 2.8.14 be pulled from distribution until they get fixed? How many people do we want to frustrate and send away, probably never to return?

I'm sticking with the version I already have. I see no point in installing 2.8.14 until it can be fixed, tested, and given the green light for download.

If would think if there are binary packages released by the GIMP team, there should be at least one round of Beta testing before any "Official" releases are made.

I think until the library problems with windows are resolved it would be indeed a good idea to pull back the window download for version 2.8.14 from the main gimp website ( http://www.gimp.org/downloads/ ) and maybe put back the link to 2.8.10 that was working good (and still is at least on my system), because 2.8.14 is unfortunately broken on win and will not really help in getting windows people that were giving a try to gimp to stay onboard.

I think this is simply not true. Don't forget, that GTK originated with Gimp as a replacement for the Motif toolkit.

In any case, there is a lot of discussion regarding moving to GTK+3 within the Gimp and Inkscape developer community. I don't think it's that simple and in fact a lot of the Linux distros have not moved to GTK+3.

Gimp is provided as an open source software and most developers are providing their time and effort without asking anything in return. Sometimes things happen. So, some patience would be nice.

Finally, even the title of this thread is not correct. Only on Linux systems, some library references were not correct. 2.8.12 Windows and Mac platforms was never effected by this. You were always free to compile it yourself as I have and 2.8.12 compiled and worked fine (http://www.mail-archive.com/gimp-develo ... 05380.html).

Hope that helps.
Partha

"Broken" isn't my words, Partha. That came directly from Mitch.

You are correct. He did say that of course.

But for me, the title of this thread seem to imply that the release itself was broken. It was not. Only the library versioning on Linux systems was broken. Anyway, it's semantics and it's already out there.

That's hilarious!

I was testing to see if there were stroke issues in Linux and RFT seems OK.

Well i am sticking with GIMP-2.8.10 for now. Unless Partha wants to share his compiled version.
For sure 2.8.14 is still having library referencing problems. Python, icons and themes, and the PDB all seem to be broken in the windows 8 64 bit version still. I haven't heard any new release information from Gimp User website either so i assume it is still a problem?

Normally, no beta testing needed. The source is available for everybody. Bugzilla is available for everybody. The range of functions for the 2.8 branch is frozen. So, after making a new release (2.8.10), bugs can be reported. The developer team try to fix a) the older bugs, b) the new bugs reported. It is not easy to track the bugs, some want to have new functions and report their wishes as bugs, some of the bugs come from a broken system and cannot be confirmed by others but most of the bugs are fixed. Those fixes are tested by the developer team shortly after they are fixed and committed to the source repository. After a while, the developer team says, "There were so many and severe bugs that we fixed, we should make a new release". Then, a new release is made.
For linux, because gimp is written and developed in and for linux.
One of the devlopers makes the official windows build and takes the newest libraries, that are also originally written for linux and bundles them to the windows release. So, the errors of the libraries (in this case gtk+ and cairo) can not be beta tested by the gimp developers. They had to beta test hundreds of libraries. In fact, they do that in many libraries, at least, they report bugs.

Hi Graechan.

Hi Rod.

Hmm, I do not have win8/64, but if the PDB would be broken, no plugin and none of the filters would work. They all make use of the PDB.
Is that right? Or what is the problem? Have you reported a bug?

I do not understand that. English is not my native language. Can you say it in other words?