Gimp 2.8 unstable for me

[SteveRiley]

Do you have ImageMagick installed? If so, run the offending file through the convert program, but keep the same extension. This will essentially write a new file, and possibly whatever was causing Gimp to choke on the original one won't survive the "conversion."

convert badfile.img goodfile.img

[Snowhog]

The problem with that is it hasn't been a 'particular' image file that has/is killing Gimp. Size of the image file doesn't seem to matter, as I've had Gimp die opening a small ones and large ones; .jpg and .png.

[SteveRiley]

Ah, it's a random(ish) thing, then. I interpreted your post #15 to mean that the sixth file was causing the crash.

Oh, wait...

Is anyone else using Gimp 2.8 on a 65-bit install

The repositories contain binaries for only 32-bit and 64-bit CPU architectures. You're gonna have to compile your own from source for that goofy 65-bit computer ya got.

[Snowhog]

You're a genuine A-?ole.

[SteveRiley]

Thank you for respecting my originality and not accusing me of being some sort of cheesy knock-off imitation A-?ole!

[Snowhog]

hehehe.

Bet I'm the only person who is running a 65-bit Kubuntu OS! Oh, ye jealous wanna-bees. Ask me politely and I might give you a copy.

[oshunluvr]

I found an old reference to GTK themes causing GIMP to crash. Might be an error in your GTK install or theme?

oxygen-gtk here

Here's my non-crashing debug output

stuart@office:~$ gimp --debug-handlers
dcraw -i '/shared/Pictures/2013/France/20130808_113634_1in.jpg'
Cannot decode file /shared/Pictures/2013/France/20130808_113634_1in.jpg
While parsing XMP metadata:
Error on line 42 char 1: End of element <exif:Flash> not expected in this context
While parsing XMP metadata:
Error on line 51 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 42 char 1: End of element <exif:Flash> not expected in this context


** (file-jpeg:6374): WARNING **: JPEG - unable to decode XMP metadata packet

Of course, I'm only running on 64 bits here, so YMMV.

[oshunluvr]

The script-fu error - did you remove the plugins folder when you re-installed?

[Snowhog]

The script-fu error - did you remove the plugins folder when you re-installed?

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.

Yep. I totally nuked every vestige of Gimp, both in / and in /home/paul and reinstalled.

Yes.

[Snowhog]

There is something 'wrong' with the installation of Gimp on my 64-bit installation. I know this to be true, because when I attempt to mark gimp for Removal or Purge in Muon Package Manager it (Muon) reports:

[SteveRiley]

That's a helpful dialog, no? It's missing the most important information: the answer to "Why?"

What does dpkg -l | grep gimp say? The first two (or three, if an error) characters in the output will give some information about the package's status:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name     Version     Architecture     Description
+++-========-===========-================-===================

[Snowhog]

No warnings or errors.

paul@tanagra:~$ dpkg -l | grep gimp
ii  gimp                                        2.8.10-0ubuntu1                       amd64        The GNU Image Manipulation Program
ii  gimp-data                                   2.8.10-0ubuntu1                       all          Data files for GIMP
ii  gimp-data-extras                            1:2.0.1-3                             all          An extra set of brushes, palettes, and gradients for The GIMP
ii  gimp-dbg                                    2.8.10-0ubuntu1                       amd64        Debugging symbols for GIMP
ii  gimp-gmic                                   1.5.7.1-4                             amd64        GREYC's Magic for Image Computing - GIMP Plugin
ii  gimp-help-common                            2.6.1-1                               all          Data files for the GIMP documentation
ii  gimp-help-en                                2.6.1-1                               all          Documentation for the GIMP (English)
ii  gimp-plugin-registry                        5.20120621ubuntu3                     amd64        repository of optional extensions for GIMP
ii  libgimp2.0                                  2.8.10-0ubuntu1                       amd64        Libraries for the GNU Image Manipulation Program
paul@tanagra:~$

[SteveRiley]

How about a simulated purge at the command line: apt-get -s purge gimp

[Snowhog]

paul@tanagra:~$ sudo apt-get --simulate purge gimp
[sudo] password for paul: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following package was automatically installed and is no longer required:
  libtiff-tools
Use 'apt-get autoremove' to remove it.
The following packages will be REMOVED:
  gimp* gimp-gmic* gimp-plugin-registry*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
Purg gimp-plugin-registry [5.20120621ubuntu3]
Purg gimp-gmic [1.5.7.1-4]
Purg gimp [2.8.10-0ubuntu1]
paul@tanagra:~$

When I've removed/purged gimp before, I did (like I do nearly 100% of all package management) so from the CLI. As you see, apt-get doesn't report it can't do what is asked. I don't know why Muon Package Manager says it can't. Strange.

[SteveRiley]

Does Muon write to any of the usual logs in /var/log/apt? Or maybe its own?