[Griatch]

GIMP 2.6.9 has been released. Please note that this is is
a release in the stable 2.6.x series, so there are only bugfixes
happening, no new features (those will appear in 2.8 hopefully
towards the end of the year).

Linux download
Windows download
Mac version is hopefully forthcoming (let us know if you see it)


Overview of Changes from GIMP 2.6.8 to GIMP 2.6.9
=================================================

* Bugs fixed:

612618 - Font selection remains visible
622234 - gimp.desktop: image/x-psd in MimeTypes twice
622196 - Unportable test(1) construct in configure script
620604 - Description of "histogram" procedure is slightly inaccurate
541586 - Tool options not saved/loaded correctly?
614153 - Importing PDF files with long titles
600112 - blur-gauss-selective.exe crashes
599233 - Dialog of "Save as BMP" ignores changes which are not made
with a mous
565001 - Text-Tool crashes when edit a 2.4.2 version xcf
565001 - Text-Tool crashes when edit a 2.4.2 version xcf
610478 - Layer preview suddenly stops getting updated
609026 - leaks shared memory
609056 - Exporting to Alias PIX format fails
608188 - a few strings in Save as... > Raw image data dialog are always
in English
604820 - GEGL Operation "path" crashes GIMP
603711 - Crashes when using path tool
607242 - GIMP 2.7.0 fails to build against libpng 1.4.0
606372 - Saving to .ppm fails on indexed colorspace
605237 - the "Antialiasing..." message in the progress bar does not show
translated
604508 - gimp-layer-new-from-visible should work from updated projection

* Updated and new translations:

Asturian (ast)
Basque (eu)
Burmese (my)
Catalan (ca)
Chinese (Hong Kong) (zh_HK)
Chinese (Taiwan) (zh_HK)
German (de)
Italian (it)
Latvian (lv)
Low German (nds)
Russian (ro)
Simplified Chinese (zh_CN)
Slovenian (sl)
Ukrainian (uk)
Valencian (ca@valencia)

[lylejk]

Wasn't going to install this one, but said what the heck. Did mess up Saul's Selective Island Script-fu, but the fix was easy enough. Wonder what other Script-fu's I have that will crash? lol

:)

[willgoss]

Made a mistake and installed this......

Now I need to go back to 2.6.8, need directions to the old files.....

I cannot understand how errors are ignored and repeated.....In my case it is Windows 7.........when you select an item on the menu it disappears.....there is a discussion on this......We solved it by using Gimp Themes.......Now that no longer works and I guess I must return to 2.6.8 if I can find it....

We still suffer with the image window not opening fully in Windows......

It is time to recognize that there are more Windows users than other versions and test before releasing.......


EDIT.......Wrong wrong wrong
Yes the menu selected lines do disappear...reinstalling 2.6.8 did not fix....you need to remove Gimp Themes and then reinstall....and now that is fixed and I can continue with 2.6.9....

[dani.user]

On windows (an operating system being used by a lot of people) the combination of a multi-windowed interface together with the fact that the main window doesn't start maximized makes using this program a real pain.

However, in 6 months since the last release, the developers seem more concerned with the fact that some strings don't get translated....

[Griatch]

dani.user said:

On windows (an operating system being used by a lot of people) the combination of a multi-windowed interface together with the fact that the main window doesn't start maximized makes using this program a real pain.

However, in 6 months since the last release, the developers seem more concerned with the fact that some strings don't get translated....

The reason the Windows version is not seeing as much development/bug fixes as Linux is simply because the main developers use Linux, not Windows. It's that simple. GIMP is an open source program, there is no concept of "pleasing the user base" - they are doing this on their free time. If Windows users are keen on a feature, they are welcome to step up and offer their time and skills to implement it in GIMP. Or maybe more Windows users could get involved in the project offering their computers to bug test the Windows build more, what do I know. It's the power and weakness of open source development - you can get what you want but you might have to actually do some work yourself to get it.
.
Griatch

[wbool63]

I have gone back to Gimp 2.6.8 after 3 days of 2.6.9 (windows XP )

My problem is that the TEXT tool (Capital A in Toolbox) appears to have a problem on my computer. When I click on a font and try to use the slider to select other fonts , the slider interface dissappears. And I am stuck with one font. The same does not happen if I use the Freetext plugin in Filters where I can select different fonts. I have tried playing with the font library in preferences . Previously if I deleted all fonts Gimp took the windows Font library.
Going back to 2.6.8 the problem is gone. I then retried 2.6.9 and the problem reappeared . I am back on 2.6.8 and there is no problem.

Note that this may be due to other causes and I have not looked at upgrading GTK yet, I also think that the Gimprc file stays the same in upgrades but again I have not looked at this. Unfortunately I do not know enough about GTK or how to debug windows except for basic stuff to take this much further.

If any of you are running Gimp 2.6.9 for windows XP could you see if the text tool works correctly so that I may determine whether there is a Gimp problem or whether I have a Windows / compatibility/ Gimp problem on my machine only.

Thanks Wbool63

[paynekj]

@wbool63 It's a bug introduced in 2.6.9:

https://bugzilla.gno...g.cgi?id=622608

[PhotoComix]

the bug is reported as fixed,...but i suppose the fix will come with a future build..or with 2.6.10

[wbool63]

Thanks Kevin and PC , I found out about 10 mins after posting.

Thanks John

[PhotoComix]

Quote

The reason the Windows version is not seeing as much development/bug fixes as Linux is simply because the main developers use Linux, not Windows. It's that simple. GIMP is an open source program, there is no concept of "pleasing the user base" - they are doing this on their free time. If Windows users are keen on a feature, they are welcome to step up and offer their time and skills to implement it in GIMP. Or maybe more Windows users could get involved in the project offering their computers to bug test the Windows build more, what do I know. It's the power and weakness of open source development - you can get what you want but you might have to actually do some work yourself to get it.
.
Griatch

and even if now more and more use linux as it was windows (as example avoiding any contact with the terminal, and strictly using only the graphic interface ) remain the fact that in linux many more end users are not afraid to "make their hand dirty " facing tasks (as example debugging, or at least reporting bugs in the right place and taking care to report w all data usuful to replicate the bugs) , tasks that almost all Windows users think strictly reserved to skilled developers

and that slow down a lot the fix of Windows only issues

[willgoss]

So with the bug ridden 2.6.9 I have returned to 2.6.8 and again reloaded Gimp Themes......

[lylejk]

Not bugs Will; features. lol

Had a long discussion at the Registry concerning the range issue change (change makes sense, but it should have been done generations ago as well as the Overlay layer bug that's still not fixed). I end up excepting change and work around them if I can. I've only reverted once to an older version of GIMP when 2.6.6 (think that was the version) came out. :)

[PhotoComix]

the bug of overlay is the most know but for me the less disturbing (in any case effect of soft light and overlay are almost identical....well in gimp are just identical for some rounding error but that doesn't make much difference )

Much More disturbing for me is the bug or anyway the difference from the PS equivalent in the color mode, difference that pop out clearly when both of layers have colours...i am not certain that the PS implementation is more correct but for sure give more interesting and nice results from a artistic point of view


Back to 2.6.9 in a ideal world in case of buggy bugfix releases, but with the new bug already fixed in the source code, the people doing the builds should just be adviced to remove the last build from repositories and if possible to replace at soon possible with a new patched version

But in the world we live now i fear that ,at least for the windows version, the build will not be removed from any of the sourceforge mirror,that no visible warnings will be visible for end users attempting to download the buggy thingy and that will remain labelled as "last stable version" till the day a 2.6.10 version will pop out

Only hope a new "unofficial" but patched build by "somebody" (hoping there is a "somebody" and that he doesn't fear to upset the responsable of the almost official windows build hosted on sourceforge ,offering something better and more updated...there is still reported GAP 2.O as the last stable version even if that poor old thing will never work with something newer then gimp 2.0 )

even then a hypotetical patched but "unofficial" build will be never visible as the official but buggy build available now....so we can wait here a for lot of complains....

[PhotoComix]

it is even possible that the last and brand new dev version 2.7.1 will b more usable

Obviously if you want something stable better stick with 2.6.8, anyway this the link for the windows installer of 2.7.1
http://sourceforge.net/projects/gimp-wi ... e/download

WARNIG 2.7.1 installer force unistall of previous version.
And for a missed or better replaced dll (intl.dll) most of extra plugins will abort at loading time.
(for this solution may be simple as copy the dll from the 2.6.x gimp bin folder and paste in the same folder of 2.7.1.
But is not a clean soluction, even if i didn't notice nasty side-effects )

[willgoss]

PC...thanks for the 2.7.1 address.........but

The installer does warn and does remove my 2.6.8 so you are committed to 2.7.1 just another poorly done Gimp release....

So after loading 2.7.1 I had to reload 2.6.8 and delete Gimp Themes and then reload Gimp Themes and I have 2.6.8 back in action......and I still have 2.7 loaded.....

While it does not have an icon it did add to the Win 7 start menu a Gimp 2 shortcut that opens 2.7.1.......

I only looked for 1 thing which is how to save....and the stupid Export requirement to save as a jpg will keep most users away from the future 2.8 release (IMO)......

But at least it is something to play with......

EDIT----
Well I gave up...after adding folders (in preferences) for other plugins and scripts got messages about missing files (Intl.dll ZLib1.dll)....then played with single window, seemed to work but on reopening lost all my docks and gave up....

I did note that on Win7 the selected menu line stopped disappearing...

[jolie]

I've updated for this bug.
541586 - Tool options not saved/loaded correctly?

That really bothered me.

I'm a scroller and usually use the dialogs to pick my font and gradients etc. so don't think I'll be bothered much by the new bug. Hopefully 2.6.10 is out soon. :)

[PhotoComix]

@willgloss

sorry i forget to mention the forced (and maybe not needed) unistall and the problems with extra plugin

I added to my previous post a warning (and a workaround for use third party plugin )

[jolie]

Does 2.7.1 also force you to uninstall if you install it on another place on your hard drive?

[PhotoComix]

Not sure Jolie
and i believe should be possible reinstall gimp 2.6 after

anyway i wrote to the dev mail list asking for info :

1 if there is some reason to force unistall 2.6 first,
2 if could be some problem to add back the intl.dll needed by most extra plugin.

in both cases i believe the answer is NO
:
1)i still have gimpainter that basically is gimp 2.6 with a couple of hacks
the installer/unistaller could not detect it because is not called "gimp"
and both seems working well
More in case you will have both 2.7 and 2.6, each will create a different gimp folder in the user directory
(a gimp-2.6 and a gimp-2.7 folder) so no possible problem for that )

2) for that dll and 3rd party plugin

the bundled plugin will search its replacement that has a different name,
the third party still will search the old dll...so paste it back should not create problems
(rename the new dll back as intl.dll seems much more risky ..i know somebody just did to use ufraw, but i fear that when using the default plugins he could have very nasty surprises )

but those are my guesses ,apparently supported by results ..but i am waiting for replies )

[jolie]

There's another thing going on when 2.6.9 is installed. In the right click menu when you click on an image it says Edit with GIMP twice now. I ended up reverting back too. Mainly because someone said uninstalling wouldn't solve it. I wanted to so see for myself. Fontunately, uninstalling did solve it. :)