Gimp 2.8.2 horrible lag. FIXED

[RPsx94]

Hello all,

I have a strange issue with GIMP that I cannot find an answer to. Whenever I use the Rectangle Select tool in GIMP, the programs suffers from...the best way to explain it is "lag".  I select an area and everything slows to a crawl, I can't select anything else,  I can't force close GIMP. It literally takes minutes for my system to allow me to move my cursor, and that is for a split second, then I have to wait minutes again for it to do anything else.  I searched the forum and the internet for symptoms like what I'm having, but nobody seems to have this issue. I did not have this issue with 2.6, it just showed up in 2.8. This issue has made GIMP totally unusable except for the most basic image painting.  

The only thing I think could have been an issue was the midi module in GIMP. I disabled it, and performance sort of picked up, but didn't help the next time I opened up Gimp.  I went in and deleted the whole module (the only way to be sure..) and then KMIX popped up asking if my Nvidia output (Video card HDMI) should be forgotten. I have a discreet soundcard in my computer, so I said yes to that.  I was pretty sure I had that Nvidia output totally disabled, as every other audio goes to my soundcard.

I'm running 32bit, system is up to date, and my computer is fairly new (built it in November).  My video card is a GTX 660.

Any help would be appreciated.  I'd like to restore my image editing capabilities back to what they were!

[Rudge]

Interesting,, I am running Gimp 2.8.2 (in LXDE and KDE, two different machines) and I am having no such slowdown when using the "Rectangle" select tool.

I can select, cut, copy, paste.. no slowdown.  

I am using a much lesser video card than you on both installs.

I don't guess this helps with your problem but perhaps it may narrow some things down when "more smarter people" investigate. 

Good Luck.  

[µT6]

same here

what type of file are you editing?

multilayer or something?

have you configured any parameter on gimp?  ram usage, redo or undo steps?

can you restore settings to default on gimp?

[RPsx94]

I'm pretty much editing JPG files (500x500) for use in MP3 tags. At most I *might* do two layers, but even copying a small part and pasting it over the

I've edited my memory usage to the max it will allow (3GB) and I think I have my undo steps to 10. My computer has 8GB Ram in it, so I don't know why upping that to 3GB would cause any issue. The odd thing is that even GIMP running by itself, or when I've got a few other programs open, gives me the same issue.

I've looked online and some have gave tips to "speed up Gimp" by turning off "Color Management", but that does nothing. I turned off desktop effects and that didn't help. I tried single window mode, mutli window mode. I tried JPG, GIF.  I changed the marching ants speed.  And I still get the same issue using the rectangle select.  I even went into Synaptic and Reinstalled Gimp, same issue.

A side issue I've had is that after I turned off Desktop Effects (and turned them back on) Synaptic/Firefox have reverted to basic square grey drop down menus, where the didn't have them before.

I hope I don't have to reinstalled PCLinux to fix either of these, I did a fresh install when I upgraded my computer back in November.

[Linuzoid]

One thing to try is to start with a fresh configuration. In root (I use Krusader), rename the .gimp-28 folder to .gimp2.8-save, and restart GIMP. You'll have to setup GIMP again to the way you like it. Another thing to try is to reinstall GIMP from the repo's.

You can also start GIMP from a terminal and see what errors it reports and post them here, a lot of times this is the best way to trouble shoot a troublesome program. 

[RPsx94]

I reinstalled GIMP and I still had issues, but deleting the gimp config file fixed the issue.

I don't know what setting would have caused the issue to crop up. I just tested it on a picture and it worked just fine.

Thank you, thank you!

[µT6]

you could have set it to default values and avoid deleting folders

anyway, good it is fixed now