GIMP AppImage (continuous integration)

Nope, still a no go.

Darktable works fine though. I really have no idea how that came about though, I don’t think I did anything from my end.

Then please run gimp from the terminal and send me the console messages… I need to see what the file-photoflow plug-in prints when it is initialized.

Thanks!

Here you go… Though it doesn’t look right, does it?

[fotonut@fotonut ~]$ gimp
This is a development version of GIMP. Debug messages may appear here.

mapped ‘/Xtns/FX-Foundry/Animation/Letter Drop’ to ‘/Filters/Extensions/FX-Foundry/Animation/Letter Drop’
mapped ‘/Xtns/FX-Foundry/Logos/Dracula’ to ‘/Filters/Extensions/FX-Foundry/Logos/Dracula’
mapped ‘/Xtns/FX-Foundry/Logos/Fiery Steel…’ to ‘/Filters/Extensions/FX-Foundry/Logos/Fiery Steel…’
mapped ‘/Xtns/FX-Foundry/Logos/Shrek Text…’ to ‘/Filters/Extensions/FX-Foundry/Logos/Shrek Text…’
mapped ‘/Xtns/FX-Foundry/Render/Gloss-Orb-Dark’ to ‘/Filters/Extensions/FX-Foundry/Render/Gloss-Orb-Dark’
mapped ‘/Xtns/FX-Foundry/Render/Gloss-Orb-Light’ to ‘/Filters/Extensions/FX-Foundry/Render/Gloss-Orb-Light’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Render’ to ‘/Filters/Extensions/FX-Foundry/Render’
mapped ‘/Xtns/Logos’ to ‘/File/Create/Logos’
gimp_display_shell_profile_update
gimp_display_shell_profile_update
gimp_display_shell_profile_update
gimp_imagefile_icon_callback: Error when getting information for file “/home/fotonut/Desktop/IMG_0394.tif”: No such file or directory

You should not have a leading dot here. In Linux ‘.’ means current directory, and you mean the path from the root dir. Try with ‘/user/bin/gimp-2.9’ instead.

Thanks @torebu, I tried that but it just launched the app via terminal…

I think one needs to force the querying of the plug-ins in order to see what I need… for this, you need to delete the pluginrc file (don’t worry, it will be re-created automatically):

rm ~/.config/GIMP/2.9/pluginrc

Then, you have to run GIMP again from the terminal and send me the console output, as you did before.

Also, could you check that the PhF plug-ins are installed in the right place? Just do

ls -lh ~/.config/GIMP/2.9/plug-ins

and post here the output…

Thanks!

[fotonut@fotonut ~] rm ~/.config/GIMP/2.9/pluginrc [fotonut@fotonut ~] gimp
This is a development version of GIMP. Debug messages may appear here.

phf_gimp query() called, phf_binary=photoflow
nread: 3
Photoflow version: 0.2.8
file-photoflow query() called, phf_binary=photoflow
stdout:
this is photoflow 0.2.8

nread: 3
Photoflow version: 0.2.8
mapped ‘/Xtns/FX-Foundry/Animation/Letter Drop’ to ‘/Filters/Extensions/FX-Foundry/Animation/Letter Drop’
mapped ‘/Xtns/FX-Foundry/Logos/Dracula’ to ‘/Filters/Extensions/FX-Foundry/Logos/Dracula’
mapped ‘/Xtns/FX-Foundry/Logos/Fiery Steel…’ to ‘/Filters/Extensions/FX-Foundry/Logos/Fiery Steel…’
mapped ‘/Xtns/FX-Foundry/Logos/Shrek Text…’ to ‘/Filters/Extensions/FX-Foundry/Logos/Shrek Text…’
mapped ‘/Xtns/FX-Foundry/Render/Gloss-Orb-Dark’ to ‘/Filters/Extensions/FX-Foundry/Render/Gloss-Orb-Dark’
mapped ‘/Xtns/FX-Foundry/Render/Gloss-Orb-Light’ to ‘/Filters/Extensions/FX-Foundry/Render/Gloss-Orb-Light’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Logos’ to ‘/Filters/Extensions/FX-Foundry/Logos’
mapped ‘/Xtns/FX-Foundry/Render’ to ‘/Filters/Extensions/FX-Foundry/Render’
mapped ‘/Xtns/Logos’ to ‘/File/Create/Logos’
gimp_display_shell_profile_update
gimp_display_shell_profile_update
gimp_display_shell_profile_update
gimp_imagefile_icon_callback: Error when getting information for file “/home/fotonut/Desktop/IMG_0391.tif”: No such file or directory

[fotonut@fotonut ~] ls -lh ~/.config/GIMP/2.9/plug-ins total 92K -rwxr-xr-x 1 fotonut users 38K May 14 07:37 file-photoflow -rwxr-xr-x 1 fotonut users 51K May 14 07:37 phf_gimp [fotonut@fotonut ~]

How do they look?

Hopefully the GIMP devs will make this much easier by making the ‘Raw image importer’ a drop-down list of currently installed RAW software in time for the 2.10 release. This way is certainly not user friendly, though it is a great step forward.

My bad!!! Everything looks OK on your side, on the other hand I have just realized that I forgot to commit to GitHub the modification that allows to make the PhF plug-in appear in the GIMP preferences!

Could you please try to delete the PhFGimp folder, and follow again the instructions for cloning, compiling and copying the PhF plug-ins?

Thanks!

1 Like

WOOHOO! GAME OVER.

Thank you!! It’s all working as expected now. :grinning:

2 Likes

Dear all,

I have once more updated my experimental version of the GIMP 2.9.5 AppImage: Filebin | 5z7hc7m62jhaptyu

It would be great if as many people as possible could test the AppImage on as many Linux distros as possible, to see if the compatibility has improved compared to the previous versions…

There is no python support yet, but I am working on it…

This AppImage is obtained by compiling most of the GIMP dependencies from sources, such that the bundled libraries are independent of what is available on the host system used for compiling (which needs to be rather old for maximum compatibility).

The building is based on jhbuild, and allows to bundle most of the libraries, including PANGO and GDK-PIXBUF. This is apparently needed to make the AppImage compatible with some Debian systems.

For anyone who is interested in the details (maybe @probono?) , the whole jhbuild configuration as well as the scripts used for building the AppImage are available on github (still under construction).

1 Like

Hi Andrea,

It launched fine, but when I loaded a .CR2 file, I got this message. Not sure it’s all that important for this test, but will no doubt pose problems further on.

Cheers.

Launched latest GIMP 2.9.5 on Debian Testing and cannot see G’MIC filters as before I have already reported. List of possible RAW importers is empty. I have Darktable installed on the system…

Thanks for checking!

G’MIC is not yet included in this experimental version… as for the rest, could you post the console messages?

I suspect that there is a library path conflict between the AppImage environment and what is needed to properly run Darktable.

Of course, I will do it later this evening as my Debian machine is at home

1 Like

Here it the output

> seg@seg-pc:~/Downloads$ ./gimp-2.9.5-20170516.glibc2.15.glibc2.15-x86_64.AppImage 
> /tmp/.mount_Ep09un/usr
> LD_LIBRARY_PATH: /tmp/.mount_Ep09un/usr/lib/:/tmp/.mount_Ep09un/usr/lib/i386-linux-gnu/:/tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/:/tmp/.mount_Ep09un/usr/lib32/:/tmp/.mount_Ep09un/usr/lib64/:/tmp/.mount_Ep09un/lib/:/tmp/.mount_Ep09un/lib/i386-linux-gnu/:/tmp/.mount_Ep09un/lib/x86_64-linux-gnu/:/tmp/.mount_Ep09un/lib32/:/tmp/.mount_Ep09un/lib64/:
> XDG_DATA_DIRS=/tmp/.mount_Ep09un/usr/bin/../share/mime:/tmp/.mount_Ep09un/usr/share/:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share
> GTK_PATH=/tmp/.mount_Ep09un/usr/bin/../lib/gtk-2.0:
> PANGO_LIBDIR=/tmp/.mount_Ep09un/usr/bin/../lib
> GDK_PIXBUF_MODULEDIR: /tmp/.mount_Ep09un/usr/bin/../lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders
> GDK_PIXBUF_MODULE_FILE: /tmp/.mount_Ep09un/usr/bin/../lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
> cat: /tmp/.mount_Ep09un/usr/bin/../lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: No such file or directory
> HERE: /tmp/.mount_Ep09un/usr/bin
> GIMP2_PLUGINDIR: /tmp/.mount_Ep09un/usr/lib/gimp/2.0
> Input parameters: ""

> Input File: 
> 	linux-vdso.so.1 (0x00007fff10cf6000)
> 	libgimpwidgets-2.0.so.0 => ././/lib/libgimpwidgets-2.0.so.0 (0x00007fb365781000)
> 	libgtk-x11-2.0.so.0 => ././/lib/libgtk-x11-2.0.so.0 (0x00007fb365144000)
> 	libgdk-x11-2.0.so.0 => ././/lib/libgdk-x11-2.0.so.0 (0x00007fb364e91000)
> 	libgimpconfig-2.0.so.0 => ././/lib/libgimpconfig-2.0.so.0 (0x00007fb364c7a000)
> 	libgimpmath-2.0.so.0 => ././/lib/libgimpmath-2.0.so.0 (0x00007fb364a74000)
> 	libgimpthumb-2.0.so.0 => ././/lib/libgimpthumb-2.0.so.0 (0x00007fb36486a000)
> 	libgimpcolor-2.0.so.0 => ././/lib/libgimpcolor-2.0.so.0 (0x00007fb364654000)
> 	libgimpmodule-2.0.so.0 => ././/lib/libgimpmodule-2.0.so.0 (0x00007fb36444e000)
> 	libgimpbase-2.0.so.0 => ././/lib/libgimpbase-2.0.so.0 (0x00007fb364223000)
> 	libgdk_pixbuf-2.0.so.0 => ././/lib/libgdk_pixbuf-2.0.so.0 (0x00007fb363ffe000)
> 	libpangocairo-1.0.so.0 => ././/lib/libpangocairo-1.0.so.0 (0x00007fb363df1000)
> 	libpangoft2-1.0.so.0 => ././/lib/libpangoft2-1.0.so.0 (0x00007fb363bdd000)
> 	libpango-1.0.so.0 => ././/lib/libpango-1.0.so.0 (0x00007fb363993000)
> 	libfontconfig.so.1 => ././/lib/libfontconfig.so.1 (0x00007fb363750000)
> 	libfreetype.so.6 => ././/lib/libfreetype.so.6 (0x00007fb3634b9000)
> 	libharfbuzz.so.0 => ././/lib/libharfbuzz.so.0 (0x00007fb36322c000)
> 	libcairo.so.2 => ././/lib/libcairo.so.2 (0x00007fb362f1d000)
> 	libgegl-0.3.so.0 => ././/lib/libgegl-0.3.so.0 (0x00007fb362c61000)
> 	libgegl-npd-0.3.so => ././/lib/libgegl-npd-0.3.so (0x00007fb362a5a000)
> 	libbabl-0.1.so.0 => ././/lib/libbabl-0.1.so.0 (0x00007fb362815000)
> 	libgio-2.0.so.0 => ././/lib/libgio-2.0.so.0 (0x00007fb362491000)
> 	liblcms2.so.2 => ././/lib/liblcms2.so.2 (0x00007fb362237000)
> 	libgexiv2.so.2 => ././/lib/libgexiv2.so.2 (0x00007fb362015000)
> 	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fb361ddd000)
> 	libmypaint-1.3.so.0 => ././/lib/libmypaint-1.3.so.0 (0x00007fb361bcb000)
> 	libgobject-2.0.so.0 => ././/lib/libgobject-2.0.so.0 (0x00007fb36197b000)
> 	libglib-2.0.so.0 => ././/lib/libglib-2.0.so.0 (0x00007fb36166c000)
> 	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fb361368000)
> 	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb36114b000)
> 	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb360dad000)
> 	libgmodule-2.0.so.0 => ././/lib/libgmodule-2.0.so.0 (0x00007fb360ba9000)
> 	libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fb360869000)
> 	libXfixes.so.3 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007fb360661000)
> 	libatk-1.0.so.0 => ././/lib/libatk-1.0.so.0 (0x00007fb36043e000)
> 	libXrender.so.1 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007fb360234000)
> 	libXinerama.so.1 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007fb360031000)
> 	libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007fb35fe21000)
> 	libXrandr.so.2 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007fb35fc17000)
> 	libXcursor.so.1 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007fb35fa0b000)
> 	libXcomposite.so.1 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007fb35f808000)
> 	libXdamage.so.1 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007fb35f605000)
> 	libXext.so.6 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fb35f3f3000)
> 	libexpat.so.1 => ././/lib/libexpat.so.1 (0x00007fb35f1c7000)
> 	libpng16.so.16 => ././/lib/libpng16.so.16 (0x00007fb35ef95000)
> 	libpixman-1.so.0 => ././/lib/libpixman-1.so.0 (0x00007fb35ecee000)
> 	libxcb-shm.so.0 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007fb35eaeb000)
> 	libxcb-render.so.0 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007fb35e8e2000)
> 	libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fb35e6ba000)
> 	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fb35e4b0000)
> 	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb35e2ac000)
> 	/lib64/ld-linux-x86-64.so.2 (0x000055af7c3aa000)
> 	libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fb35e095000)
> 	libexiv2.so.14 => ././/lib/libexiv2.so.14 (0x00007fb35dbe8000)
> 	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fb35d866000)
> 	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fb35d64d000)
> 	libjson-c.so.2 => ././/lib/libjson-c.so.2 (0x00007fb35d442000)
> 	libffi.so.6 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007fb35d23a000)
> 	libpcre.so.3 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fb35cffc000)
> 	libXau.so.6 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fb35cdf6000)
> 	libXdmcp.so.6 => /tmp/.mount_Ep09un/usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fb35cbf0000)

> /tmp/.mount_Ep09un/usr/bin/gimp.bin --pdb-compat-mode=on ""
> This is a development version of GIMP.  Debug messages may appear here.

> phf_gimp query() called, phf_binary=photoflow
> file-photoflow query() called, phf_binary=photoflow
> file-photoflow query(): failed to run photoflow (photoflow)
> exec_path: darktable
> darktable: /tmp/.mount_Ep09un/usr/lib/libtiff.so.5: no version information available (required by /usr/bin/../lib/x86_64-linux-gnu/darktable/libdarktable.so)
> darktable: /tmp/.mount_Ep09un/usr/lib/libtiff.so.5: no version information available (required by /usr/lib/libGraphicsMagick-Q16.so.3)
> darktable: /tmp/.mount_Ep09un/usr/lib/libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20)
> darktable: /tmp/.mount_Ep09un/usr/lib/libdbus-1.so.3: no version information available (required by /usr/lib/x86_64-linux-gnu/libavahi-client.so.3)
> darktable: relocation error: /lib/x86_64-linux-gnu/libgcrypt.so.20: symbol gpgrt_lock_lock, version GPG_ERROR_1.0 not defined in file libgpg-error.so.0 with link time reference
> gimp_display_shell_profile_update
> gimp_display_shell_profile_update
> gimp_display_shell_profile_update

This is the knot of the rope… I’m looking for a solution, but it is not obvious…

I’m using OpenSuse. How do you uninstall/remove GIMP Appimage? I’ve tried using Zypper or Yast but they just try to uninstall GIMP from the repositories where I have the unstable version.

You just delete the appimage file.

1 Like

Here is an update concerning the GIMP 2.9.x AppImage package.

I have just uploaded a new test package on filebin.
This new package should support all compatible python plug-ins, like the previous test version.
Moreover, it should now load the Darktable and Photoflow plugins correctly, and fix the problems reported by @Fotonut and @Benja1972 a while ago.

If you are interested to know why invoking the external Darktable executable from within the AppImage is not trivial, and why it took so long to fix the problem, you can have a look at this thread: Should an exec wrapper be used? · Issue #396 · AppImage/AppImageKit · GitHub

I’d really appreciate if people could test this new version and report back if things are now working properly.

next steps will be the inclusion of G’MIC and nUFraw.

Thanks!

1 Like

Hey @Carmelo_DrRaw, almost, but no cigar!