[Apfhex]

I have the Gimp.app 2.0.0-2 package, and when X11 launches, I am presented with this:


At one point with the previous 2.0.0 package, it opened fully with all the windows, yet everywhere there should have been text, there wasn't, making it next to impossible to use.

I haven't messed around with X11 at all, and I don't have Fink installed (this shouldn't matter since the .app package is supposed to include everything I need to run GIMP).

Any thoughts? (also, I know 2.0.0-3 was just released, I'll download and try it, though I highly doubt it will fix my problem)

[Krypton]

That looks like the setup stage. If you expanded the window some more to the right, there ought to be some options such as 'Ok' and 'Cancel'. This stage can take a good few minutes so maybe patience is in order.

Of course, if the solution isn't that simple I'm sorry I couldn't think of something more helpful.

[Apfhex]

I could tell it was the setup window. I've tried expanding it (which reveals more blank white space) and I've let it sit there for a while and nothing happens.

Now with 2.0.0-3, when it launches, NOTHING happens, except that my CPU usage goes to 100%, with "sh" taking up about 15% (I don't even know where the other 85% is coming from, looking at Activity Viewer, but it's mostly from the system, indicated in red).

BTW, I also tried this in my clean "test" user account, and it does the same thing.

[slow moe]

One of the great new features of 2.0.0-3 is it recognizes your native fonts automagically, problem is it's broke and hangs on startup when reading the fonts, or so I hear.

Use 2.0.0-2, and follow the directions I posted in another Gimp thread for native/custom font support.



About your original problem with 2.0.0-2, open a terminal and enter:

ls -a ~

You should see two hidden folders named ".gimp-2.0" and ".gimp-2.0-etc". Remove them. Again, in a terminal enter:

rm -rf ~/.gimp-2.0

And:

rm -rf ~/.gimp-2.0-etc

Now, rerun Gimp.

[Apfhex]

Thanks for the advice, though I had already tried doing that with 2.0.0-2, to no avail.

At least I wasn't the only one with the problem in 2.0.0-3. I just grabbed 2.0.0-4 and now it works!