Thanks again Francois. I quite like the single window view, although as you say it doesn't really add that much to the program.
What it does help to do, is to stop potential users saying "The Gimp looks weird" :)
I'll learn to live with it as is.

This behavior (closing image and Gimp at once) did exist in 2.8.6 already. If you disable th single window view, you'll get the possibility to close the image and keep the program open when closing the image window. Unfortunately, closing the "Tools" window now only closes the Tools window instead of closing everything at once.
As the single-window view brought nothing but a Photoshop-like look, you can try to uncheck it.

Thanks for the replies. Yes, now you mention it I remember seeing something about it and skimming over it at the time. Slight nuisance to me TBH. If I'm working on a series of images, I have to remember to leave the last one open, and then close it after loading the next. Not a big deal, just one of those things. Options for some of this behaviour would be nice if such a thing is possible.

Michael, yes I agree, closing the program if the last image is closed is a good ergonomic improvement. You can still use File > Close view. With the former three-window interface the problem did not exist: when you closed the left window, everything was closed, and when you closed the image window the image was closed and the program remained open. The single-window view introduced many drawbacks, which were very difficult to fix.

IIRC, closing the program if the last image is closed (via the window's close aka [x]) button, at least) is a deliberate change for single window mode only.

Apparently, some users think that this is how it should work, and someone agreed. I don't, but I don't use the single window mode, either ;)

First off, many thanks for the work put into The Gimp by the developers.
Has anyone got any idea why with the last version and this one, I seem to have lost the ability to close the present image and leave the program open with a blank background. No big deal, but I still keep forgetting and closing the program rather than just the image.
Working on Win 7 64 bit. Thanks.

Yeah, I suspected that much. But for the sake of completeness, it would be nice if someone who's active on gimpchat could ask samj that this was indeed sufficient, and add that information to the User Filter announcement.

Regarding the Python no-show problem: yeah, I've seen some of those posts somewhere. What I'm not seeing is a bug report, and so the problem doesn't exist and won't be fixed.

The only current Python-related bug I'm aware of is about Python plug-ins being queried at every launch (and not being added to pluginrc file). But unfortunately it has not been reproduced - and we have tried hard to do this in a session on our #gimp irc channel:
https://bugzilla.gnome.org/show_bug.cgi?id=711491

I forgot to thank you and all the developers for making GIMP better and better Michael. I've found nothing wrong with 2.8.8 itself; the fix was a backwards compatibility issue with the User filter and it was remedied. I did hear others have had some issues with python w.r.t. the 32-bit version and I have no idea what that could be since 2.8.8 64-bit python works fine for me. Very much looking for the 2.10 fork; hope that the RGGJAN extraction ability can somehow be part of it but I understand from what others have stated that it isn't a good fit for reasons that I won't elaborate here. That said, having 16/32 bit edit ability is going to make GIMP the lead image editor; trust me. I've seen way lot of interests in other forums since PS did their shenanigans. :)

Thank's Michael! :)

If you are referring to the windows version, then the installer on http://www.gimp.org/downloads/ contains both 32 bit and 64 bit versions.

Hi!

Where can I find 64 bits of this version (if exists)?

Thank's

I assume a recompile with a more recent Glib was sufficient. The gimpchat thread and the readme file in the package don't mention any additional complication, at least.

P.S. I'm seeing some other "$problem found/does still exist" posts in some forums around, that's why I'd like to repeat my previous warning:

If a bug is not reported at https://bugzilla.gnome.org, it does not exist. If it gets fixed by a future update, then that is pure luck.

Sorry; posted quickly the solution and didn't read your comment Michael. Yes, the userfilter is ancient. lolol

Still, it's quite a fun and, to me, useful filter and am glad that samj recompiled it with 2.8.8 in mind. :)

Have to brag about samj now. She fixed userfilter for 64-bit GIMP. :)

http://gimpchat.com/viewtopic.php?f=7&t=6653&p=115830#p115814

The change in Glib that causes this is described in https://mail.gnome.org/archives/commits-list/2013-February/msg07050.html

Does that User Filter binary you're using qualify as ancient?

Just confirmed; removed path for User Filter (via GIMP interface for plugins) and all's well except, of course, the User Filter is no longer. Need to fix this. Maybe someone can recompile it or tell me how too; would be much appreciated. :)

The problem turns out not with GIMP itself, but with the User Filter. Below are the errors. Maybe the User filter needs to be re-compiled. Sorry for not analyzing the errors earler (work weekend nights and last night was my Friday if you will and tired I was then and just installed the GIMP 2.8.8 before hitting the sack). Still not sure how the new version breaks the User Filter and I use this filter often enough that I hope there's a fix for it shortly. :)

http://imageshack.us/a/img109/9082/1l9o.png
http://imageshack.us/a/img203/2692/vkqe.png
http://imageshack.us/a/img713/8582/ow7t.png

If you read through those bug reports, you'll find that e.g. the Ubuntu bug has been forwarded to the GNOME Bugzilla and was identified there as a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=681845

And that one is supposed to be fixed. Since 2012-11-05.

If this happens again, then the platforms that were used use an older version of GTK+, the bug has been reintroduced or it is a different bug with the same or similar symptoms.

The crash after saving a JPEG file on Linux has been reported since V 2.6 as far as I remember, but it happens with 2.8.6 and Ubuntu 12.04 64-bit. It does not happen always, but especially when you "export" a file you have not "saved" before, but sometimes when the file has been "saved" too. This severe bug has been reported many times. It is discussed here:
http://www.gimpchat.com/viewtopic.php?f=8&t=4915
here:
http://askubuntu.com/questions/275767/gimp-crashes-on-jpeg-save
here:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1067514
It already existed in 2004:
http://www.archivum.info/debian-bugs-dist.lists.debian.org/2004-12/04170/Bug-285504-gimp-crashes-when-click-on-save-(png-or-jpeg)---saving-larges-images.html
This is the reason why I did not report it again.
And I don't believe in Gimp's future any longer, alas.
True improvements would be:
- 16-bit images at last
- a real Overlay mode
- adjustment layers
Not a b*** Save/export separation that has been asked by nobody, messed the code, and does not exist in any software. The guy who invented that must have been paid by Adobe, or he is a maniac. Not even in LibreOffice as it was said: Libroffice SAVES in ODT, doc, docx, RTF, etc (all word processor formats). It EXPORTS in PDF, which is a nearly non-editable format.

There are no such problems known or reported yet. On the contrary, all feedback so far has confirmed that several bugs have indeed been fixed.

If you don't report what you see as a bug, then waiting will achieve nothing at all.

Installed GIMP 2.8.8 from ftp site. It launches fine, but during the launch, I get errors with libglib-2.0-0. Not sure the solution. Guess I will have to tolerate this until they fix it. :)

Windows installer is now available from
http://www.gimp.org/downloads/

Please note that this page adjusts to your platform, i.e. you won't see the Windows downloads by default with a non-Windows system and vice-versa. The HTTP link might not yet work, stick to the FTP one.

The installers have been moved from Sourceforge to ftp.gimp.org because of all those §$%&& ads on SF that tricked users into downloading useless other software or tampered installers.

Let's wait for Partha's build, Lyle!
Not a big deal considering time between releases, you're right, Roman.
I never noticed the bugs fixed here; the traditional crash on Linux after saving a JPEG is not mentioned in the fixes, so I suppose it is still there!
The Save/export stupidity is a brilliant advance in ergonomics, the .png default extension when you need a jpeg too.
Gimp is a predeceased software, with no alternative, alas!

Still no Window installer yet, but I'll wait. :)

it's ok i guess, not a big deal considering the time between releases

Awsome, thank u gimp developers/