GIMP doesn't start in disco dev

Bug #1820088 reported by shemgp
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gimp (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hello,

Gimp doesn't start when running in Disco Dingo with error in terminal:

gimp: symbol lookup error: /usr/lib/libgimpcolor-2.0.so.0: undefined symbol: gegl_buffer_iterator2_new

I have libbabl:
Package: libbabl-0.1-0
Version: 0.1.62-1

otto's gimp-edge PPA works.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gimp 2.10.8-2
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 15 00:13:44 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (1263 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gimp
UpgradeStatus: Upgraded to disco on 2019-02-16 (26 days ago)

Revision history for this message
shemgp (shemgp) wrote :
Revision history for this message
Doug McMahon (mc3man) wrote :

Gimp from Disco repo works fine here, recent fresh install of 19.04. Your install is some long time upgrade mishmash

Revision history for this message
shemgp (shemgp) wrote :

Works for me now too.

Changed in gimp (Ubuntu):
status: New → Fix Released
Revision history for this message
gunwald (gunwald) wrote :
Download full text (5.7 KiB)

I have the same issue on an freshly updated Ubuntu. Can somebody enlighten me, how this can be fixed? I found some hints, that there might me an old version of the library libbabl in /usr/local be causing the problem, but does not seem to be the case:

$ ldd /usr/bin/gimp
 linux-vdso.so.1 (0x00007fff6b50e000)
 libgimpwidgets-2.0.so.0 => /usr/lib/libgimpwidgets-2.0.so.0 (0x00007f5223130000)
 libgtk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 (0x00007f5222ce6000)
 libgdk-x11-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 (0x00007f5222c2f000)
 libgimpconfig-2.0.so.0 => /usr/lib/libgimpconfig-2.0.so.0 (0x00007f5222c18000)
 libgimpmath-2.0.so.0 => /usr/lib/libgimpmath-2.0.so.0 (0x00007f5222c11000)
 libgimpthumb-2.0.so.0 => /usr/lib/libgimpthumb-2.0.so.0 (0x00007f5222c05000)
 libgimpcolor-2.0.so.0 => /usr/lib/libgimpcolor-2.0.so.0 (0x00007f5222bea000)
 libgimpmodule-2.0.so.0 => /usr/lib/libgimpmodule-2.0.so.0 (0x00007f5222be2000)
 libgimpbase-2.0.so.0 => /usr/lib/libgimpbase-2.0.so.0 (0x00007f5222bb1000)
 libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007f5222b8b000)
 libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007f5222b7b000)
 libpangoft2-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007f5222b62000)
 libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007f5222b15000)
 libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f5222acf000)
 libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f5222a14000)
 libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007f522291b000)
 libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x00007f52227fb000)
 libgegl-0.4.so.0 => /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0 (0x00007f5222549000)
 libgegl-npd-0.4.so => /usr/lib/x86_64-linux-gnu/libgegl-npd-0.4.so (0x00007f522233f000)
 libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007f5222176000)
 libbabl-0.1.so.0 => /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 (0x00007f5222092000)
 liblcms2.so.2 => /usr/lib/x86_64-linux-gnu/liblcms2.so.2 (0x00007f5222038000)
 libgexiv2.so.2 => /usr/lib/x86_64-linux-gnu/libgexiv2.so.2 (0x00007f5222015000)
 libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f5221ff9000)
 libmypaint-1.3.so.0 => /usr/lib/x86_64-linux-gnu/libmypaint-1.3.so.0 (0x00007f5221fe4000)
 libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007f5221f88000)
 libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f5221e67000)
 libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f5221d19000)
 libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f5221d13000)
 libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f5221cf2000)
 libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5221b05000)
 libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007f5221aff000)
 libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f52219c5000)
 libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f52217bf000)
 libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007f522179600...

Read more...

Revision history for this message
Dan Martin (bithooked) wrote :

I also have this issue after an upgrade from 18.10. I don't see how this is NOT a bug. Simply working on a clean install doesn't make this a non-issue. Ubuntu is still expected to cleanly upgrade. I tried uninstalling and reinstalling Gimp and the Gimp libraries. It doesn't fix the issue.

The only good news I have is that the Snap Store version does work. I had to uninstall the apt release, and install the snap.

Revision history for this message
Mario Di Nicola (warp99) wrote :

I had libgegl-0.4-0 from Otto's PPA that was claiming to be newer than the version in Disco. I used Synaptic to force downgrade to the Disco version, now everything works fine. It could be this or you have an old version of libgegl in /usr/local/bin from another install.

Revision history for this message
JohnShep (john-boxrec) wrote :

Thanks fix worked for me

sudo apt purge gimp
sudo apt purge libgegl-0.4-0
sudo apt install gimp

Revision history for this message
Miguel Belardinelli Prytoluk (prytolukster) wrote :

Have been updating since 16.04, now on Disco and JohnShep's fix works for me also.
Agree with Dan Martin. "Works on a clean install" is not a good argument. This is a bug.

Revision history for this message
Michael Schumacher (schumaml) wrote :

One of the ways to be sure this doesn't happen would be to force a purge of everything that has been installed from third-party repositories, do a clean upgrade, and re-install any pruged packages from the Debian repos. With some big What-Ifs remaining when said packages happen to e.g. not be available.

This could be a bug of, or likely rather a change to, the Ubuntu upgrade policy (as in "people involved in Ubuntu decide how such cases are to be handled in general), but I am not familiar with the current policy at all.

Revision history for this message
Michael Schumacher (schumaml) wrote :

Ugh, it's obviously too early... that was meant to read

"[..] do a clean upgrade, and re-install any purged packages from the Ubuntu repos [...]"

and not supposed to imply that packages from Debian should be mixed into an Ubuntu system by default.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.