Gimp 2.8 unstable for me

[Snowhog]

Prior to upgrading to 14.04 on my 64-bit laptop, Gimp 2.8 ran perfectly. Since the upgrade, Gimp is prone to just quiting -- it just winks out of existance. This also happens if I start Gimp and try to open "some" image files (plain jpg images); Gimp winks out of existance.

I took the time this morning to completely get rid of Gimp, and I mean completely. Then I updated the package cache and dist-upgraded. I rebooted and using Muon Package Manager, installed Gimp. The same issue happens.

I don't know where to begin to isolate why this is happening. I like Gimp. I'm used to Gimp. I would like Gimp to behave normally, as it did previously.

Is anyone else using Gimp 2.8 on a 65-bit install of 14.04 and NOT having this problem, or, if you did but fixed it, how did you do so?

[claydoh]

I have not used it extensively, not much at all, really, but it has worked as expected, no crash or closings. I do have many if not all the plugins available from the repos installed, inclufing x-foundry and g-mic. I can't make a crash.

You might check if you have any plugins or scripts in your local configs, maybe one of those is causing this, and maybe activate the error console.

[NoWorries]

I use Gimp 2.8 extensively, particularly since I have just returned from 5 weeks overseas. When I have any trouble with Gimp, my first approach is to delete the home directory file .gimp-2.8. Have you done this already and are still having problems?

[Snowhog]

Yep. I totally nuked every vestige of Gimp, both in / and in /home/paul and reinstalled. No change. Gimp decides to just wink out of existence.

I'm using Krita (for the first time) today, and find it rather easy to use (for what I need an image editor for), and, dare I say, more powerful, and it behaves.

[NoWorries]

I am wondering if you have more than one computer with 14.04 installed, and if Gimp is behaving the same? If you have one and you have separate partitions for root and home, then a reinstall might save a lot of time and frustration. When I have odd behaviour, that is what I resort to, as it can be done in less than two hours wall clock time with a broadband connection.

[whatthefunk]

Ive noticed Gimp behaving weird lately too. I havent had it quit, but I cant move some windows and sometimes the tools just stop working.

[NoWorries]

Sorry, but I have forgotten the obvious, which is, what output does Gimp give when launched from the command line? Hopefully that give some worthwhile output as on my system it gives nothing as it works perfectly.

[Snowhog]

Gimp, launched from the CLI. Starts up just fine. I then attempted to open a .jpg image and Gimp winked out of existence. This is what the CLI showed:

paul@tanagra:~$ gimp
*** Error in `gimp': free(): invalid next size (fast): 0x0000000004c9dff0 ***
gimp: terminated: Aborted

(script-fu:25042): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
paul@tanagra:~$

[NoWorries]

I just did a google search on the error LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error and found several hits. One suggestion was to not only remove and reinstall gimp but also include other related packages such as libgimp2.0. It might be worth checking out the error message with Google as others have had this problem.

[Snowhog]

libgimp2.0 is installed. I know all are trying to help, and it is all appreciated.

As I said, I had purged/nuked/ every vestige of Gimp from my 64-bit system other than packages/libraries used by Gimp but shared by other applications. Once Gimp was 'no more', including removing gimp releated hidden directories in /home/paul, I reinstalled Gimp and the same misbehavior remained.

Gimp behaved correctly in 13.10. So, I don't know if it is something about 14.04, KDE 4.13.1, or a combination of both. Gimp is the only program (of those that I use regulary) that misbehaves.

[NoWorries]

Looks like it could be KDE 4.13.1 as I have 4.13.0 as shown in the attached graphic. So I think it would be appropriate for you to submit a 4.13.1 bug report as I would not be very pleased if this feature existed when it is released.

[NoWorries]

I have just finished updating all my computers to KDE 4.13.1. I tested each one in turn with Gimp and it worked on all of them without a hitch. I am wondering if Snowhog's problems have now been resolved.

[Snowhog]

I don't think so. I'll try Gimp this evening when I get home and reply with the results.

[oshunluvr]

try installing gimp-dbg then launching gimp from the cli with --debug-handlers

[Snowhog]

paul@tanagra:~$ gimp --debug-handlers
lcms: skipping conversion because profiles seem to be equal:
 sRGB IEC61966-2.1
 sRGB built-in
lcms: skipping conversion because profiles seem to be equal:
 sRGB IEC61966-2.1
 sRGB built-in
lcms: skipping conversion because profiles seem to be equal:
 sRGB IEC61966-2.1
 sRGB built-in
While parsing XMP metadata:
Error on line 41 char 1: End of element <exif:Flash> not expected in this context
While parsing XMP metadata:
Error on line 54 char 1: End of element <exif:Flash> not expected in this context

Metadata parasite seems to be corrupt
While parsing XMP metadata:
Error on line 41 char 1: End of element <exif:Flash> not expected in this context

** (file-jpeg:15009): WARNING **: JPEG - unable to decode XMP metadata packet
*** Error in `gimp': free(): invalid next size (fast): 0x0000000003ddc310 ***
gimp: terminated: Aborted

(script-fu:14098): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
paul@tanagra:~$

The last line above after opening a sixth image file (the other five opened fine and I closed them).