GIMP 2.10.0-RC1 AppImage available for download

From my Travis-powered automated GIMP AppImage building machinery, here comes a freshly produced 2.10.0-RC1 AppImage ready for download.



Thank you!

Do you confirm that it works fine for you? Could you tell me which Linux distro/version you have?


Hmm. Doesn’t fly on my Ubuntu 16.04:

DIR: /tmp/.mount_TxZbxh
System stdc++ library: "/usr/lib/x86_64-linux-gnu/"
System stdc++ library version: "3.4.21"
Bundled stdc++ library version: "3.4.22"
Newest stdc++ library version: "3.4.22"
Using bundled stdc++ library
GDK_PIXBUF_MODULEDIR: /tmp/.mount_TxZbxh/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders
GDK_PIXBUF_MODULE_FILE: /tmp/.mount_TxZbxh/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
# GdkPixbuf Image Loader Modules file
# Automatically generated file, do not edit
# Created by gdk-pixbuf-query-loaders from gdk-pixbuf-2.36.0
# LoaderDir = ././/lib/gdk-pixbuf-2.0/2.10.0/loaders
"ani" 4 "gdk-pixbuf" "Windows animated cursor" "LGPL"
"application/x-navi-animation" ""
"ani" ""
"RIFF    ACON" "    xxxx    " 100

"tiff" 5 "gdk-pixbuf" "TIFF" "LGPL"
"image/tiff" ""
"tiff" "tif" ""
"MM *" "  z " 100
"II* " "   z" 100
"II* \020   CR\002 " "   z zzz   z" 0

"ico" 5 "gdk-pixbuf" "Windows icon" "LGPL"
"image/x-icon" "image/x-ico" "image/x-win-bitmap" "image/" "application/ico" "image/ico" "image/icon" "text/ico" ""
"ico" "cur" ""
"  \001   " "zz znz" 100
"  \002   " "zz znz" 100

"qtif" 4 "gdk-pixbuf" "QuickTime" "LGPL"
"image/x-quicktime" "image/qtif" ""
"qtif" "qif" ""
"abcdidsc" "xxxx    " 100
"abcdidat" "xxxx    " 100

"xbm" 4 "gdk-pixbuf" "XBM" "LGPL"
"image/x-xbitmap" ""
"xbm" ""
"#define " "" 100
"/*" "" 50

"xpm" 4 "gdk-pixbuf" "XPM" "LGPL"
"image/x-xpixmap" ""
"xpm" ""
"/* XPM */" "" 100

"jpeg" 5 "gdk-pixbuf" "JPEG" "LGPL"
"image/jpeg" ""
"jpeg" "jpe" "jpg" ""
"\377\330" "" 100

"bmp" 5 "gdk-pixbuf" "BMP" "LGPL"
"image/bmp" "image/x-bmp" "image/x-MS-bmp" ""
"bmp" ""
"BM" "" 100

"tga" 4 "gdk-pixbuf" "Targa" "LGPL"
"image/x-tga" ""
"tga" "targa" ""
" \001\001" "x  " 100
" \001\t" "x  " 100
"  \002" "xz " 99
"  \003" "xz " 100
"  \n" "xz " 100
"  \v" "xz " 100

"icns" 4 "gdk-pixbuf" "MacOS X icon" "GPL"
"image/x-icns" ""
"icns" ""
"icns" "" 100

"svg" 6 "gdk-pixbuf" "Scalable Vector Graphics" "LGPL"
"image/svg+xml" "image/svg" "image/svg-xml" "image/vnd.adobe.svg+xml" "text/xml-svg" "image/svg+xml-compressed" ""
"svg" "svgz" "svg.gz" ""
" <svg" "*    " 100
" <!DOCTYPE svg" "*             " 100

"png" 5 "gdk-pixbuf" "PNG" "LGPL"
"image/png" ""
"png" ""
"\211PNG\r\n\032\n" "" 100

"pnm" 4 "gdk-pixbuf" "PNM/PBM/PGM/PPM" "LGPL"
"image/x-portable-anymap" "image/x-portable-bitmap" "image/x-portable-graymap" "image/x-portable-pixmap" ""
"pnm" "pbm" "pgm" "ppm" ""
"P1" "" 100
"P2" "" 100
"P3" "" 100
"P4" "" 100
"P5" "" 100
"P6" "" 100

"gif" 4 "gdk-pixbuf" "GIF" "LGPL"
"image/gif" ""
"gif" ""
"GIF8" "" 100

GIMP2_PLUGINDIR: /tmp/.mount_TxZbxh/usr/lib/gimp/2.0
Input parameters: ""

Input File: 
ldd: bin/gimp.bin: No such file or directory

/gimp.bin --pdb-compat-mode=on ""
/tmp/.mount_TxZbxh/AppRun: line 129: bin/gimp.bin: No such file or directory

The file is significantly smaller than my previous AppImage (150M vs 184 for 2.9.7)

Confirmed, I am testing a fix…

I prepared a new package, and updated the links in the two posts I wrote… this one works OK for me on Ubuntu 17.04, and should also include this important bug fix. However, I didn’t have time yet to test it on other Linux versions.

Could you please check if the new package works on your 16.04 system as well?

1 Like

@Carmelo_DrRaw good work, the AppImage runs fine here in Sabayon. It took about 60 seconds to start it the first time, most of that time was spent on the plugins. Starting it a second time took 5 seconds.


Longer start times on first launch is an appimage thing, for sure.

Works in Mint 18.3
What’s new?

1 Like

Second one works on Bodhi 4.0

1 Like

The long plugin loading time at the first run is due to the fact that the plugin cache has to be re-built, and new plugins are read from an AppImage that gets de-compressed on-the-fly.
Nothing one can do to mitigate this…

New version works OK. Strangely, if you have a 2.8 instance up, it won’t start and will pass the buck to the 2.8 instance…

Thanks, seems to be working fine with Debian 9.

1 Like

Actually a problem with that version, Python scripts are unable to register:

File "/home/me/.config/GIMP-AppImage/2.10/plug-ins/", line 41, in <module>
from gimpfu import *
ImportError: No module named gimpfu

The strange thing is that the same import works in the Python-fu console.

Could you post the full console output from the appimage? Maybe we can find an hint there…

I found that the 2.9.7 AppImage has the same problem…

The problem is only with the user’s plugins (search “ofn-” to find my scripts), the standard python plugins (foggify, slice…) register normally but they seem to have a slightly different python environment if I trust the logs.

Attached, full execution with --verbose after removing the pluginrc file to force the re-registration of everything. (7.0 KB)

Edit: the difference between standard plug-ins and mine is that the plugins in the app image use the shebang:

#!././/bin/env python

(sic) while mine use:

#!/usr/bin/env python

which is the shebang as found in the standard scripts pulled from Git.

If I change the shebang in my script to match the one used in the AppImage scripts, then my script registers correctly.

I think I understand what happens… so far, the only way I could find for running the python-based plugins in the AppImage is to bundle the python interpreter in the AppImage itself. The python from the host system seems not to work properly in combination with the gimp executable in the AppImage, but this aspect definitely requires more testing.

I’m running your Gimp 2.10.0 appimge in Linux Mint 18.3. It runs well, but G’mic wont load and gives this error:

Could not execute plug-in “gmic_gimp_qt”
because it uses an obsolete version of the plug-in protocol.

No need to copy the gmic plugin in ~/.config, it is already included. Could you please delete it and try again?

Ah yes, deleting the file fixes the issue. Thanks for that!