gimp crashes

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

http://people.ubuntu.com/~pitti/ddebs is not reponding right now so I can't get the package at that site (I will try it later today/tomorrow).

I installed gimp-dbg and have attached what I got.

Error while reading shared library symbols:
Cannot find new threads: generic error

The first time I executed it, it opened normally. Then I closed it and told it to run again and it had a similar (but not identical) crash to the problem I reported originally.

Since it says there is an error with shared libraries, I am guessing that one of the dependencies is incorrect on my system (I have not upgraded everything to feisty-- just a few select items like gimp because I wanted to assist with testing the ubuntustudio-graphics meta package but did not want to install everything for feisty). Just guessing, one of the dependencies for gimp in feisty might need a version correction.

In an strace, before deleting the old .gimp-2.2 settings, the program stops at this line:

15:34:55.559985 futex(0x84629a8, FUTEX_WAIT, 2, NULL

after that, the program opens properly. When I exit from that, the strace has a bit of an error message:

15:39:42.984437 unlink("/home/matthew/.gimp-2.2/gimpswap.13810") = -1 ENOENT (No such file or directory)

If you want that entire strace I can add it; it is really quite large, so I will wait to be asked for that one. After the directory has been regenerated, it finishes with an strace that looks the same as the first one. The start-up screen says "looking for data files: modules"

Correction in case the following is confusing:
After the directory has been regenerated, it finishes with an strace that looks the same as the first one. The start-up screen says "looking for data files: modules"

After the directory has been regenerated gimp starts fine and works fine (as far as I can tell). After exiting gimp, when I attempt to execute it again, I get the same problem as before and the strace looks the same.

sorry; I seem to have missed half of the directions for the backtrace; that first one is probably not very useful.

Sorry I probably jumped ahead here; hopefully from what I got you can figure out what was the problem. I feel fairly certain it was a dependency problem because after an apt-get install of all of the gimp things I had, it now works properly.

matthew@silas:~$ sudo apt-get install gimp-data gimp-dbg gimp-print gimp-python gimp-svg gimp-dcraw gimp-help-en gimp-perl gimp-python gimp-data-extras

This was a problem resulting from a partial upgrade to feisty (before release) and, as I recall, was a result of a dependency not requiring the appropriate version of a required library. I am marking it as rejected so people don't need to worry about it any more.

do you remember what depends needed to be updated?

I don't really remember for certain... I think the command above fixed it, but I may have updated libgimp2.0 or libgtk2.0 or libc6 and not thought about it at the time. I added Feisty repos to my sources list and then did 'apt-get install gimp' (along with a few other things) and after starting gimp once it wouldn't start again until I deleted the config file (~/.gimp-2.2) and then removed feisty repos-- I didn't want the instability problems with everything. This isn't a problem someone doing a dist-upgrade would have; only if you had packages from edgy AND feisty would this happen.

Back then, I thought I fixed it by running

apt-get install gimp-data gimp-dbg gimp-print gimp-python gimp-svg gimp-dcraw gimp-help-en gimp-perl gimp-python gimp-data-extras

but I wonder if I didn't install those libraries, too by installing/upgrading something else. Would it have been gimp-data or gimp-data-extras (do those include the files that it would have been processing when it crashed)?

Sorry I don't know for certain; if I had a spare system I would install edgy and try to reproduce the problem (to see if it is fixed or not).

--Matthew

letting the bug closed then, feel free to reopen if you run into it again and can provide the details on the Depends which needs to be updated