GIMP 2.8.18 & 2.9.4 Released

lylejk · **Joined:** Sep 24, 2010 **Posts:** 12829

You may first make sure your Win8/10 is a 64-bit OS. That said, you then may want to back up your filters/presets and such and do a complete un-install before re-install. I don't believe the install uninstalls your previous version of GIMP; just upgrades it.

Wallace · **Posted:** Sun Jul 17, 2016 2:12 pm **(#22)**

RMDesigns wrote:

Is there a way to tell which version you have once installed?
I have an old version of GIMP for running old scripts if that makes any difference.

Inquiring minds want to know!
:gimp

Happy Sunday,
Larry

Is Program 64/32-bit With Task Manager

Open Task Manager, click More Details then select the Details tab.

Right click any column header and choose Select columns.

Find and check the Platform box, click OK.

Run Gimp and look at the Platform column in the Task Manager.
This column tells you if it is 32-bit or 64-bit.

The processes explained above is for Windows 8 or 10.

In Windows 7 the process is slightly different.
Select the Processes tab.
You'll see the list of processes that are running.
If a program is 32-bit,
near its name you will see the text: *32.
If a program is 64-bit,
you will only see its name,
without *32 at the end.

RMDesigns · **Joined:** Mar 13, 2016 **Posts:** 83

OK. I'll do a clean install and then reinstall my old version if that's the way Wilber rolls! LOL :gimp

Yes I have an x64 system, I quit drinking years ago! :mrgreen:

Thanks for the info Lyle.

Update: I didn't have to do a clean install. GIMP does remove old program versions and does a new install, not an upgrade. All I had to do is reinstall my old version after it finished. Then I checked the versions in the task manager (thanks Wallace) and it is 64 bit.

Note: GIMP does put the 64 bit program files in the (x86) 32 bit file folder. Not a big deal to me but worth noting. You can change that location if you do a custom install. OK enough, I'm happy now! :mrgreen:

RMDesigns · **Joined:** Mar 13, 2016 **Posts:** 83

@Wallace
Thanks for the reply, good information.
Larry

Wallace · **Posted:** Sun Jul 17, 2016 2:54 pm **(#25)**

RMDesigns wrote:

@Wallace
Thanks for the reply, good information.
Larry

iggy · **Posted:** Sun Jul 17, 2016 4:22 pm **(#26)**

I'm running Xubuntu 16.04LTS and I have currently installed GIMP 2.8.16. (And I'm trying to figure if I should get this new 2.8.18.)

1) What is the security risk they refer to? (I looked at the link, something about an attacker supplying code, but I didn't understand it.) Does it apply to me or only Windows and OSX computers?

2) My GIMP 2.8.16 is loaded with fonts and brushes. Is there an easy way of transferring them to the new GIMP?

3) (granted, kind of a vague question) 2.8.16 works fine for me. Am I going to be shooting myself in the foot to get 2.8.18? You know, having to learn the new features etc.?

Thanks.

Odinbc · **Posted:** Sun Jul 17, 2016 8:15 pm **(#27)**

1) GIMP 2.8.18 notes.
2) Everything stays as is.
3) GIMP 2.8.18 is not a critical upgrade, it fixes a vulnerability. For Ubuntu flavours a PPA (ppa:otto-kesselgulasch/gimp), is the easiest way to keep GIMP & G'MIC current. At the link you'll notice 'gimp', (2.8.x current stable) & 'gimp-edge', (2.9.x development). Both PPA include G'MIC. If you don't want to bother with a PPA and normally get GIMP from Xubuntu Software Centre, you'll have to wait for the next system upgrade.

iggy · **Posted:** Mon Jul 18, 2016 2:27 pm **(#28)**

Odinbc wrote:

1) GIMP 2.8.18 notes.
2) Everything stays as is.
3) GIMP 2.8.18 is not a critical upgrade, it fixes a vulnerability. For Ubuntu flavours a PPA (ppa:otto-kesselgulasch/gimp), is the easiest way to keep GIMP & G'MIC current. At the link you'll notice 'gimp', (2.8.x current stable) & 'gimp-edge', (2.9.x development). Both PPA include G'MIC. If you don't want to bother with a PPA and normally get GIMP from Xubuntu Software Centre, you'll have to wait for the next system upgrade.

Thanks Odinbc. But back to my #1 question. I did read that release note and really didn't understand it? "executing arbitrary code provided by the attacker" I don't know what that means. What is the security risk for me (a non-techie) in non-tech-speak? Am I vulnerable to getting a virus? What?

lylejk · **Joined:** Sep 24, 2010 **Posts:** 12829

Hey, iggy. The way I understood the issue, it was if you opened an XCF file. My be is you rarely open any XCF files other than the ones that you create yourself. Definitely be weary of XCF files shared even from here of course, but supposedly the developers patched this particular exploit.

iggy · **Posted:** Mon Jul 18, 2016 8:08 pm **(#30)**

lylejk wrote:

Hey, iggy. The way I understood the issue, it was if you opened an XCF file. My be is you rarely open any XCF files other than the ones that you create yourself. Definitely be weary of XCF files shared even from here of course, but supposedly the developers patched this particular exploit.

Thanks Lyle. Ah, I never even thought of that. I know it's really hard to get a virus from a .jpg but I never thought about an .xcf. I suppose I can just scan any .xcf files before I open them. (Or get the new GIMP.) Question. "My be..." I'm guessing "best estimate"?

rich2005 · **Joined:** Mar 04, 2011 **Posts:** 2611

iggy wrote:

....snip....
What is the security risk for me (a non-techie) in non-tech-speak? Am I vulnerable to getting a virus? What?

Using linux, so small as to not worth worrying about.

iggy · **Posted:** Tue Jul 19, 2016 1:35 pm **(#32)**

rich2005 wrote:

iggy wrote:

....snip....
What is the security risk for me (a non-techie) in non-tech-speak? Am I vulnerable to getting a virus? What?

Using linux, so small as to not worth worrying about.

Ah, that's what I like to hear. Thanks Rich.