Your message dated Thu, 13 Aug 2020 13:29:32 +0100 with message-id <20200813122932.ga491...@espresso.pseudorandom.co.uk> and subject line Re: Bug#968342: libgegl-sc-0.4.so: undefined symbol: __exp_finite has caused the Debian Bug report #968342, regarding libgegl-sc-0.4.so: undefined symbol: __exp_finite to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 968342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: gimp Version: 2.10.8-2 Severity: grave Justification: renders package unusable Dear Maintainer, Gimp does not start anymore (even after new install) $ gimp GEGL-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/seamless-clone.so' load error: /lib/x86_64-linux-gnu/libgegl-sc-0.4.so: undefined symbol: __exp_finite GEGL operation missing! GIMP requires the GEGL operation "gegl:seamless-clone". This operation cannot be found. Check your GEGL install and ensure it has been compiled with any dependencies required for GIMP. So it it not possible anymore to use Gimp. On an other computer we have the same issue. It worked before. -- System Information: Debian Release: 10.5 Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data 2.10.8-2 ii libaa1 1.4p5-46 ii libbabl-0.1-0 0.1.62-1 ii libbz2-1.0 1.0.6-9.2~deb10u1 ii libc6 2.31-2 ii libcairo2 1.16.0-4 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.10.1-2 ii libgcc-s1 [libgcc1] 10-20200211-1 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgegl-0.4-0 0.4.12-2 ii libgexiv2-2 0.10.9-1 ii libgimp2.0 2.10.8-2 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgs9 9.27~dfsg-2+deb10u3 ii libgtk2.0-0 2.24.32-3 ii libgudev-1.0-0 232-2 ii libharfbuzz0b 2.3.1-1 ii libheif1 1.3.2-2~deb10u1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-3 ii liblzma5 5.2.4-1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.3-0 1.3.0-2.1 ii libopenexr23 2.2.1-4.1 ii libopenjp2-7 2.3.0-2+deb10u1 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpangocairo-1.0-0 1.42.4-8~deb10u1 ii libpangoft2-1.0-0 1.42.4-8~deb10u1 ii libpng16-16 1.6.36-6 ii libpoppler-glib8 0.71.0-5 ii librsvg2-2 2.44.10-2.1 ii libstdc++6 9.2.1-8 ii libtiff5 4.1.0+git191117-2~deb10u1 ii libwebp6 0.6.1-2 ii libwebpdemux2 0.6.1-2 ii libwebpmux3 0.6.1-2 ii libwmf0.2-7 0.2.8.4-14 ii libx11-6 2:1.6.7-1 ii libxcursor1 1:1.1.15-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii xdg-utils 1.1.3-1+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gimp recommends: ii ghostscript 9.27~dfsg-2+deb10u3 Versions of packages gimp suggests: pn gimp-data-extras <none> pn gimp-help-en | gimp-help <none> pn gimp-python <none> ii gvfs-backends 1.38.1-5 ii libasound2 1.1.8-1 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 0.4.18-1 On Thu, 13 Aug 2020 at 13:24:54 +0100, Simon McVittie wrote: > On Thu, 13 Aug 2020 at 12:38:00 +0200, W Forum W wrote: > > Gimp does not start anymore (even after new install) > > > > $ gimp > > GEGL-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/seamless-clone.so' > > load error: /lib/x86_64-linux-gnu/libgegl-sc-0.4.so: undefined symbol: > > __exp_finite > > This is fallout from upgrading glibc to 2.31. It appears to have > been fixed as a side-effect of build system changes in gegl 0.4.18, so > upgrading to the version of gegl from testing/unstable should fix this. > > This can only affect partial upgrades from Debian 10 'buster' to > testing/unstable or the future Debian 11 'bullseye'. Pure Debian 10 systems > are unaffected, and so are pure testing/unstable systems. Closing the bug on that basis, now that it has been reassigned to the right package. smcv
--- End Message ---
