Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Gimp 2.10.6 fails to start on Kubuntu 18.04
#1
I've just installed gimp 2.10.6 on Kubuntu 18.04 from the ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu repository, but when I try to start it I get a pop-up with the following message:

     GdkPixbuf version too old!

     GIMP requires GdkPixbuf version 2.30.8 or later.  Installed GdkPixbuf version is 2.30.7.
 
     Somehow you or your software packager managed
     to install GIMP with an older GdkPixbuf version.

     Please upgrade to GdkPixbuf version 2.30.8 or later.

however, according to synaptic, the version of gdkpixbuf on my system is 2.36.11-2....

I tried starting it from a console, and the pop-up was preceded by the following message:

     ~$ gimp
     Missing fast-path babl conversion detected, Implementing missing babl fast paths
     accelerates GEGL, GIMP and other software using babl, warnings are printed on
     first occurance of formats used where a conversion has to be synthesized
     programmatically by babl based on format description

     *WARNING* missing babl fast path(s): "Y u16" to "Y' u8"
     GEGL-Message: 23:05:49.279: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/pixbuf.so'
     load error: /usr/lib/x86_64-linux-gnu/gegl-0.4/pixbuf.so: undefined symbol: gdk_pixbuf_read_pixels

does anyone have any idea how to fix this?
Reply
#2
Quote:.. Please upgrade to GdkPixbuf version 2.30.8 or later.
however, according to synaptic, the version of gdkpixbuf on my system is 2.36.11-2.....

..and that is the only version for ubuntu bionic

Did you have say, the kesselgulasch/gimp-edge packages installed? If so, have you disabled that repo in synaptic.

My (k)ubuntu 18.04 VM has(had) gimp-edge installed. To get Gimp 2.10.6 installed and running I had to remove Gimp and related packages.

This is the synaptic history. screenshot: https://i.imgur.com/6jEZPFk.jpg
removed gimp gimp-data
removed libgimp2.0
removed libgegl libgtk2-perl
installed gimp which pulled in the updated libbabl and libgegl packages.

You could just try updating libgegl but I would purge anything Gimp and start again. Your gimp profile will remain, that is not lost.

Quote:I tried starting it from a console, and the pop-up was preceded by the following message:

Apart from the GEGL message, the first part is usual: https://i.imgur.com/6S6O4s6.jpg
Reply
#3
(08-23-2018, 08:40 AM)rich2005 Wrote:
Quote:.. Please upgrade to GdkPixbuf version 2.30.8 or later.
however, according to synaptic, the version of gdkpixbuf on my system is 2.36.11-2.....

..and that is the only version for ubuntu bionic

Did you have say, the kesselgulasch/gimp-edge packages installed? If so, have you disabled that repo in synaptic.

My (k)ubuntu 18.04 VM has(had) gimp-edge installed. To get Gimp 2.10.6 installed and running I had to remove Gimp and related packages.

This is the synaptic history. screenshot: https://i.imgur.com/6jEZPFk.jpg
removed gimp gimp-data
removed libgimp2.0
removed libgegl libgtk2-perl
installed gimp which pulled in the updated libbabl and libgegl packages.

You could just try updating libgegl but I would purge anything Gimp and start again. Your gimp profile will remain, that is not lost.

Quote:I tried starting it from a console, and the pop-up was preceded by the following message:

Apart from the GEGL message, the first part is usual: https://i.imgur.com/6S6O4s6.jpg
I had removed gimp and gimp-data, but not the others. I'll give it a try...
Reply
#4
(08-23-2018, 06:19 PM)alpreston Wrote:
(08-23-2018, 08:40 AM)rich2005 Wrote:
Quote:.. Please upgrade to GdkPixbuf version 2.30.8 or later.
however, according to synaptic, the version of gdkpixbuf on my system is 2.36.11-2.....

..and that is the only version for ubuntu bionic

Did you have say, the kesselgulasch/gimp-edge packages installed? If so, have you disabled that repo in synaptic.

My (k)ubuntu 18.04 VM has(had) gimp-edge installed. To get Gimp 2.10.6 installed and running I had to remove Gimp and related packages.

This is the synaptic history. screenshot: https://i.imgur.com/6jEZPFk.jpg
removed gimp gimp-data
removed libgimp2.0
removed libgegl libgtk2-perl
installed gimp which pulled in the updated libbabl and libgegl packages.

You could just try updating libgegl but I would purge anything Gimp and start again. Your gimp profile will remain, that is not lost.

Quote:I tried starting it from a console, and the pop-up was preceded by the following message:

Apart from the GEGL message, the first part is usual: https://i.imgur.com/6S6O4s6.jpg
I had removed gimp and gimp-data, but not the others. I'll give it a try...
I had the kesselgulash/gimp (2.10.6) package installed, (not gimp-edge, which appears to be gimp 2.99). i did previously remove gimp 2.8 before attempting to install 2.10.6. (If i disable the repo, synaptic reverts to offering gimp 2.8.) I have since removed all the packages you suggested (which also took out some other stuff like sane, etc.), and reinstalled gimp 2.10.6, following the steps in your synaptic history (noting that one of the files you removed, libgutenprintui2-1, wasn't previously installed on my system).     I'm still getting the same error.
Reply
#5
I have since tried installing 2.10.6 on two other Kubuntu 18.04 systems to see if the same problem was replicated. On one it launched without crashing, but on the other, I get a similar but different pop-up. It complains that my version of the liblcms libraries is too old when in fact they are current. This is getting weird!
Reply
#6
You might have to go a few further steps.

As it happens, my desktop computer, installed new shiny SSD drive (3 weeks old today), has Kubuntu 18.04

I did initially try kesselgulasch/gimp 2.10 but decided I wanted Gimp 2.8.22 + the Gimp 2.10.x flatpak.

That is the state at the moment. See if I can replace Gimp 2.8 with Gimp 2.10

Enabling the kesselgulasch/gimp ppa and updating synaptic these are marked as upgradable but I can see that will break gimp packages.

screenshot: https://i.imgur.com/IUaaYEB.jpg


What is missing from that upgrade, the gegl packages.

If I then go to the installed libgegl-0.3-0 and mark for complete removal I get this, pulls in dependencies and upgrades gimp.

Gimp 2.10 uses libgegl-0.4 https://i.imgur.com/0viGFNd.jpg

Forgot to disable the gimp 2.8 profile, pulled in scripts/plugins that give errors but Gimp 2.10 works.

https://i.imgur.com/TSgm5bC.jpg

Now, to fire up that backup snapshot to restore the kubuntu partition back to what it was Wink
Reply
#7
(08-24-2018, 09:01 AM)rich2005 Wrote: You might have to go a few further steps.

As it happens, my desktop computer, installed new shiny SSD drive (3 weeks old today), has Kubuntu 18.04

I did initially try kesselgulasch/gimp 2.10 but decided I wanted Gimp 2.8.22 + the Gimp 2.10.x flatpak.

That is the state at the moment. See if I can replace Gimp 2.8 with Gimp 2.10

Enabling the kesselgulasch/gimp ppa and updating synaptic these are marked as upgradable but I can see that will break gimp packages.

screenshot: https://i.imgur.com/IUaaYEB.jpg


What is missing from that upgrade, the gegl packages.

If I then go to the installed libgegl-0.3-0 and mark for complete removal I get this, pulls in dependencies and upgrades gimp.

Gimp 2.10 uses libgegl-0.4 https://i.imgur.com/0viGFNd.jpg

Forgot to disable the gimp 2.8 profile, pulled in scripts/plugins that give errors but Gimp 2.10 works.

https://i.imgur.com/TSgm5bC.jpg

Now, to fire up that backup snapshot to restore the kubuntu partition back to what it was Wink
Yeah, when I first installed the kesselgulash/gimp ppa, it pulled in libgegl-0.4 alongside 0.3; on the second try and on one other system, I deleted libgegl-0.3.0.That didn't seem to make any difference to the resulting crashes. So far, the only commonality I've found between the two machines it's crashing on, are that they are Kubuntu 18.04 running on Intel i5, whereas the one it loads on is an AMD box, though I don't know if that's at all relevant.
Reply
#8
Yes, my old desktop is a 4core AMD. Could be a hardware issue. Not willing to upgrade my kubuntu 16.04 Intel laptop to check Wink
Reply
#9
SOLVED: It turns out the two machines did have older versions of gdk-pixbuf and lcms tucked away in /usr/local/lib. After removing them, Gimp starts up normally. Hopefully, removing them hasn't broken the packages that were using them.
Reply


Forum Jump: