GIMP just went limp

Briefly describe your issue below:

After the latest update (today) I saw that GNU radio among another 400+ updates were done. Unfortunately, GIMP keeps crashing now.

Reinstall via synaptic did nothing to fix this

What version of Parrot are you running? (include version (e.g. 4.6), edition(e.g. Home//KDE/OVA, etc.), and architecture (currently we only support amd64)

Linux parrot 5.2.0-2parrot1-amd64 #1 SMP Debian 5.2.9-2parrot1 (2019-08-25) x86_64 GNU/Linux

PRETTY_NAME="Parrot GNU/Linux 4.7" NAME="Parrot GNU/Linux" ID=parrot ID_LIKE=debian VERSION="4.7" VERSION_ID="4.7" HOME_URL="" SUPPORT_URL="" BUG_REPORT_URL=""

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)

Configured to multiboot with other systems? (yes / no)

If there are any similar issues or solutions, link to them below:
none seen

If there are any error messages or relevant logs, post them below:

Crash report

GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
	Using built-in specs.
	Target: x86_64-linux-gnu
	Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
	Thread model: posix
	gcc version 9.2.1 20190827 (Debian 9.2.1-6) 
using GEGL version 0.4.12 (compiled against version 0.4.14)
using GLib version 2.60.6 (compiled against version 2.60.6)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

fatal error: Segmentation fault

Stack trace:



Apparently, the update should not have been included for Debian derivitives, including Parrot yet

Debian Bug report logs - #939768

Debian Bug report logs: Bugs in package gimp (version 2.10.8-2+b1) in unstable;package=gimp#_0_1_4

Good catch.I guess we have to wait for a fix.Or install it with Snap or with Flatpak.I prefer Flatpak since it is more maintained and its on their website. ~ Flatpak ~ Snap

1 Like

yea I was in the middle of some graphic work for another website…I usually wait to run updates till the end of the day, but that day I did it in the morning and killed my graphic work.

So it looks like here is what happened:

GIMP 2.10.8-2 was built on sid (which had GEGL 0.4.12 at the
time). Testing also had GEGL 0.4.12, so there was no version mismatch
and everything was fine. Then, GIMP 2.10.8-2+b1 was built on sid, which
now has GEGL 0.4.14. When GIMP 2.10.8-2+b1 (now built against GEGL
0.4.14) migrated to testing (which still has GEGL 0.4.12), the version
mismatch occurred causing the GIMP to crash.

Note that I am just guessing the versions of packages that sid and
testing had in the past, so it should be taken with a grain of salt.

If this is the case, there appears to be three obvious fixes:

  1. Migrate GEGL 0.4.14 to testing.
  2. Revert the testing GIMP package to 2.10.8-2.
  3. Build the testing GIMP package against GEGL 0.4.12.

Since GEGL is 188 days old and should be migrated anyway, 1. seems to be
preferable. Looking at the package tracker [1], it appears that there
are some migration issues that need to be looked at, so perhaps 2. could
be a temporary fix. I’m not sure how 3. would be implemented, since the
sid GIMP package would still need to be built against GEGL 0.4.14.

so it looks like the peeps at Debian figured out the bug and made a change to the library as noted here

I’m guessing we need same or similar changes in our repositories so that GIMP can be used again…but that’s above my paygrade , I guess we need one of the ParrotSec Dev Team to make the needed changes…

Apparently, the issue gets fixed by installing libgegl-0.4-0
0.4.14-2 from “unstable” over 0.4.12-2 from “testing”.