If you enable colour management, drawing becomes impossible, gimp slows down so much that the brush moves jaggedly. With colour management disabled it works fine.

On a positive note, I just compiled wavelet decompose plugin and it works just fine. I'll see if GMIC works soon.


...whoops, I forgot I already had gmic in my home plugin directory. Yeah it works.

Aha.

I do not have such problems. Maybe:

I have an Intel i7-870, maybe it is fast enough so gimp doesn't slow down. (what kind of Processor do you have?)
You have a picture, that is complex and I took just a cheap picture to test it. (can I have one?)
I have done some changes in gimp, so it is linked againt liblcms2-2, that is maybe faster (I send the changed data)

Hatti

OnkelHatti,
My box has an AMD Phenom II X4 925 processor and 8GB RAM.
I have the same problem.
I tried Gimp-2.9.1,same problem!
Gerard.

Edit:If it was an lcms problem then why doesn't gimp-2.6 suffer from it?
Also have a look at this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=645345
Especially Mitch's reply at the end.

if it wasn't already mentioned in this thread, gimp.org is now officially announcing it too, so it's really "officially out" now.

I have a build environment here, but I'm in no rush after 3.5 years. I'll wait before the 2.8 package hits Debian SID.

I'm not looking forward to having to re-do my Beginning GIMP tutorial ... gah.
.
Griatch

I hear you Griatch.
Fun times ahead!

GIMP gimp-2.8.0-setup.exe released!!!
http://sourceforge.net/projects/gimp-wi ... P%202.8.0/

Thanks for the heads up pogogogo. I indeed uninstalled RC1 and installed 2.8 full. Of course 2.6.12 got uninstalled again (but I will fix that later). They fixed the tif but, but still MM's Labcurves program won't work (but sigmoidal contrast does). The jpeg preview save size bug still exists though (not sure why this didn't get addressed). Also, gimprc error (which prevents the path for both pspi and user filter to exist concurently) also exists, but I have to have PSPI so I'll live with the Filter Factory convertor fiasco (each time I run the user filter, I have to point to the guf files) for now. Looks like that won't get fixed; sad for me. Not sure if there is a brush sluggish issue yet since I haven't tested that but I believe others have said it's still there. Anyway, I'm going to parallel post this respont at gimpusers too since maybe the developers read stuff there more then here. All in all, only the tif bug appears to have gotten fixed between rc1 and now.

Lylejk i didn't try because from long i don't use PSPI but i believe this workaround may fix :

1)load gimp,
2) use the userfilter setting the correct path
3) without closing gimp, start explorer as admin, search the gimprc file, enter propriety
...and check the "read only" box

obviously in case you will want change again something in the gimp preferences you will need first to make again the file writable, but for that you just need to unmark the same box

if your diagnosis is correct what i suggest should fix

Never thought to make the gimprc read only. Will give that a shot PC and will either edit this post for follow up with yea or nea.

edit:

Did not work PC; at least the entry didn't get removed. lol

Will now go back to the way it was (and do the fixes so Impressionist will work again; Paint Engine too).

Sorry that doesn't work
I am not going to install 2.8 now i am waiting for a partha (or samj) portable, better if at 64 bit

But at soon i got i will look also to that and see if i may found some solution (if the new build didn't already solve )

Anyone using installed gimp from otto-kesselgulasch ppa? That warning of breaking OS has me reluctant. Tried to install from source but too many dependencies need compiling. Should I wait until it gets into the package manager? Or is the otto ppa ok?

Ok, I was messing around with things and I managed to somehow break my gimp 2.8 installation... I tried to uninstall, recompile and install it again, it seems to compile & install ok but I keep getting this error when trying to run it:

gimp: error while loading shared libraries: libgimpwidgets-2.0.so.0: cannot open shared object file: No such file or directory

Anyone know what's up with this...?

Ok, nvm, I figured it out... turns out all I had to do was sudo ldconfig.

That's what I love about linux - you keep learning new stuff all the time.

Just had to say some praise (despite a few issues that hopefully get resolved with the 2.8.1 release) for GIMP 2.8 (using the 64-bit version). 2.8 has yet locked up on me; would do so several times a day sometimes with GIMP 2.6.x (32-bit version). I won't say it hasn't crashed on me though but at least I've not lost any work because of it (and, I believe, it crashed maybe 3 times; won't even tell you how buggy 2.6x was even at 2.6.12 release. lol). It was fun trying to figure out the bugs in GIMP too and enjoyed the little participation I had with that. So many folks found work-a-rounds and such too which made going to a now true native 64-bit GIMP enjoyable. Again, just had to give the developers and definitely the folks here who have actively (and still are) ironing the kinks my greatfulness and praise.