Hello, I have downloaded GIMP 2.9.5 AppImage. It works wonderfully on my version Linux Mageia 6. Also, my GIMP 2.8.22 installation continues to run in parallel. What does not work on GIMP 2.9.5 AppImage is the plug in Gmic. I have not found it in the package even though it is described:
“G’MIC plug-in version 1.7.5” is already included in this test version.
Ciao. Ernesto
It works (2.9.9-20180315 plus gmic)! Thanks for your help 
Ciao.Ernesto
1 Like
I happened to try this version an hour ago, on Ubuntu Studio 17.10 though, GMI’C worked fine and also updated the filters and external data without problems.
1 Like
Hi Carmelo_DrRaw, I already work now without problems with the version GIMP 2.9.9. applmage plus gmic that you linked to me. Is there the same package in version 2.10? Sorry I’m a bit unsure because there are so many versions now. 
Ciao. Ernesto
@ernesto You can get a 2.10.1 package from the same release page: gimp-git-2.10.1-20180428.glibc2.15-x86_64.AppImage.
The development packages (those with a gimp-git- prefix) are build on a weekly basis, typically on Thursday evening, so you can have a look there regularly for updates…
I have some troubles building some of the plug-ins for the official 2.10.0 release (it is a known problem), so I am waiting for the first bugfix version to make a new release package.
where did you get gimp 2.10.1 from? or is this just a git snapshot from the 2.10 branch?
I am cloning the GIMP_2_10_0 tag from the GNOME git repository. I will check if the official tar file of the 2.10.0 sources has this fixed.
The same problem exists in the official tar file from Index of /gimp/v2.10/.
This is what is written in gimp.pc.in:
Requires: gdk-pixbuf-2.0 >= @GDK_PIXBUF_REQUIRED_VERSION@ cairo >= @CAIRO_REQUIRED_VERSION@ gegl-0.3 >= @GEGL_REQUIRED_VERSION@
Thank you for your prompt reply. I do not understand where I can find the release page. 
Ciao. Ernst
not sure why you would think that requires mean that your gimp would be version 2.10.1.
@ernesto https://github.com/aferrero2707/gimp-appimage/releases/download/continuous/gimp-git-2.10.1-20180428.glibc2.15-x86_64.AppImage
Sorry, I mixed up the version numbers in the discussion… yes, 2.10.1 simply corresponds to the version reported by the current git HEAD.
so you could just build from the 2.10.0 tag?
This is actually what my build scripts are doing for point releases: they fetch the corresponding git tag instead of the git HEAD. However, the current GIMP_2_10_0 git tag suffers with the same issue as the release tarball, namely a not-up-to-date gimp.pc.in file…
bug link?
I can only quote the corresponding email discussion: http://www.gimpusers.com/forums/gimp-developer/20596-gimp-pc-in-still-contains-reference-to-gegl-0-3
I have updated the GIMP AppImage scripts to automatically bundle the .scm scripts available from the Pixls.us repository.
At each build, the .zip file of the repository is downloaded, extracted, and the .scm files are copied to the usr/share/gimp/2.0/scripts folder in the AppImage bundle, so that the should be readily available without any further installation.
hence, the number of available filters in the AppImage should grow together with the GIMP-Scripts repository…
Please let me know if you encounter any issues.
2 Likes
One more update for the GIMP AppImage: the bundled code is now supposed to be fully relocatable. This means that the internal launcher does not change anymore the working directory, and images passed on the command line can be opened also if their path is not absolute.
The last package is available here. I would appreciate any feedback as usual…
2 Likes
Working well for me so far.
1 Like