GIMP AppImage (continuous integration)

Colin_Adams · September 25, 2016, 7:07pm

Actually, I’m not so sure.

I took a picture today that I might want to print. After exporting it from darktable as a 32-bit tiff, I shall want to import it into GIMP 2.95 to make use of G’MIC’s Octave sharpening. I don’t think there will be any advantage to me in doing it in a colour space other than sRGB, but I could be wrong.

paperdigits · September 25, 2016, 7:15pm

Consumer level photo-oriented inkjets can surely cover the sRBG gamut with ease; if you know your printer can cover a larger gamut, why not make use of it?

Colin_Adams · September 25, 2016, 7:21pm

Ah. I didn’t know that. Still learning.

How do I find out what gamut my printer (HP Photosmart premium 309g) can cover?

Colin_Adams · September 25, 2016, 7:38pm

I actually believed the opposite was the case. Because darktable appears to tell me that is so:

I have a profile for the printer/paper combination from the paper’s manufacturer. When I do a gamut check in darktable with that profile set, it shows most of the dark background out of gamut. If i change that profile to sRGB, it shows almost nothing out of gamut. Am I misunderstanding what darktable is telling me?

paperdigits · September 25, 2016, 7:53pm

That printer is essentially 4 color (has photo black and matte black + YMK) so I’m not surprised at the gamut coverage. I’d get 6 or more colors for good gamut coverage. With your setup in particular, sRBG might be your best bet.

Carmelo_DrRaw · September 25, 2016, 8:21pm

This might be the effect of the different black level of your printer compared to sRGB.

In other words, the blackest black that your printer can print is lighter than the pure black encoded in sRGB. Therefore the darkest sRGB colors are considered out-of-gamut, because they cannot be rendered on paper…

Colin_Adams · September 27, 2016, 2:37pm

The G’MIC filter is working fine.

But when I try to print, I can’t see my printer. No such problem in GIMP 2.8 (Fedora 24)

paperdigits · September 27, 2016, 4:03pm

The gmic filter is applied correctly, no problem thereafter, but if I choose new layer as the output, it is not renamed according to the filter I used, as it is in gimp 2.8. Not a huge deal, as I just rename it, but it was nice polish.

Carmelo_DrRaw · September 27, 2016, 5:28pm

Does this happen also with the "standard Gimp 2.9? Maybe @David_Tschumperle knows something more?

Colin_Adams · September 28, 2016, 8:34am

Perhaps I shouldn’t have mentioned G’MIC.
If I run the AppImage, and do nothing but open a file, and then Ctrl-P, I see no printer.

Is printing supposed to be working in 2.9.5? Or do i have to export my image as an 8-bit image, and then open 2.8 for printing?

Carmelo_DrRaw · September 28, 2016, 11:33am

I have no printers configured on my Linux system, so I never checked… maybe there is some incompatibility between the appimage and the underlying printing system. I will have a look.

rich2005 · September 28, 2016, 1:43pm

Kubuntu 16.04, Brother J825DW printer, wireless connection.

Printing works here: This an image with precision set to 32-bit fp and regular print setup.
http://imgur.com/79N1AYS
Gutenprint also working: Get a warning which was not there previously, I still have that previous appimage but it might be my system which updates often. & it does print.

If you already have gutenprint on your Gimp 2.8.x an easy setup is copy the file printrc from ~/.gimp-2.8 to ~/.config/GIMP-AppImage/2.9

Colin_Adams · September 28, 2016, 1:53pm

I haven’t used gutenprint, so perhaps that is why I don’t have a printrc file.
I DO have a print-settings file in both. Maybe I could just copy the 2.8 one to the 2.9 directory?

Colin_Adams · September 28, 2016, 2:06pm

Alas, it makes no difference.

Carmelo_DrRaw · September 28, 2016, 5:03pm

I have added a dummy printer to my Linux system and then tried to print an image file with the AppImage… for me, the printer correctly shows in the print dialog:

Is this what doesn’t work for you?

Colin_Adams · September 28, 2016, 5:07pm

Yes. I see no printers there. I don’t even see a Print To File line.

Carmelo_DrRaw · September 28, 2016, 5:20pm

Can you send me a copy of the terminal output? You’ll need to run the appimage from the terminal to get it…

Colin_Adams · September 28, 2016, 5:24pm

[colin@colin Downloads]$ ./gimp*
/tmp/.mount_E5foed/usr
LD_LIBRARY_PATH: ./lib/:./lib/i386-linux-gnu/:./lib/x86_64-linux-gnu/:./lib32/:./lib64/:…/lib/:…/lib/i386-linux-gnu/:…/lib/x86_64-linux-gnu/:…/lib32/:…/lib64/:
XDG_DATA_DIRS=/tmp/.mount_E5foed/usr/bin/…/share-mime:./share/:
GTK_PATH=/tmp/.mount_E5foed/usr/bin/…/lib/gtk-2.0:
GDK_PIXBUF_MODULEDIR: /tmp/.mount_E5foed/usr/bin/…/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders
GDK_PIXBUF_MODULE_FILE: /tmp/.mount_E5foed/usr/bin/…/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
cat: /tmp/.mount_E5foed/usr/bin/…/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: No such file or directory
HERE: /tmp/.mount_E5foed/usr/bin
GIMP2_PLUGINDIR: /tmp/.mount_E5foed/usr/lib/gimp/2.0
Input parameters: “”

Input File:
linux-vdso.so.1 (0x00007ffd065d7000)
libgimpwidgets-2.0.so.0 => ././/lib/libgimpwidgets-2.0.so.0 (0x00007fb53b8f5000)
libgtk-x11-2.0.so.0 => ././/lib/libgtk-x11-2.0.so.0 (0x00007fb53b2b8000)
libgdk-x11-2.0.so.0 => ././/lib/libgdk-x11-2.0.so.0 (0x00007fb53b005000)
libgimpconfig-2.0.so.0 => ././/lib/libgimpconfig-2.0.so.0 (0x00007fb53adef000)
libgimpmath-2.0.so.0 => ././/lib/libgimpmath-2.0.so.0 (0x00007fb53abe9000)
libgimpthumb-2.0.so.0 => ././/lib/libgimpthumb-2.0.so.0 (0x00007fb53a9de000)
libgimpcolor-2.0.so.0 => ././/lib/libgimpcolor-2.0.so.0 (0x00007fb53a7c8000)
libgimpmodule-2.0.so.0 => ././/lib/libgimpmodule-2.0.so.0 (0x00007fb53a5c2000)
libgimpbase-2.0.so.0 => ././/lib/libgimpbase-2.0.so.0 (0x00007fb53a39c000)
libgdk_pixbuf-2.0.so.0 => /lib64/libgdk_pixbuf-2.0.so.0 (0x00007fb53a155000)
libpangocairo-1.0.so.0 => ./lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007fb539f48000)
libpangoft2-1.0.so.0 => ./lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007fb539d32000)
libpango-1.0.so.0 => ./lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007fb539ae5000)
libfontconfig.so.1 => /lib64/libfontconfig.so.1 (0x00007fb5398a2000)
libfreetype.so.6 => ./lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fb5395fe000)
libharfbuzz.so.0 => ./lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007fb5393a9000)
libcairo.so.2 => ./lib/x86_64-linux-gnu/libcairo.so.2 (0x00007fb53909d000)
libgegl-0.3.so.0 => ././/lib/libgegl-0.3.so.0 (0x00007fb538de1000)
libgegl-npd-0.3.so => ././/lib/libgegl-npd-0.3.so (0x00007fb538bda000)
libbabl-0.1.so.0 => ././/lib/libbabl-0.1.so.0 (0x00007fb538996000)
libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007fb538611000)
liblcms2.so.2 => ././/lib/liblcms2.so.2 (0x00007fb5383b7000)
libgexiv2.so.2 => ./lib/x86_64-linux-gnu/libgexiv2.so.2 (0x00007fb538197000)
libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007fb537f45000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fb537c37000)
libz.so.1 => /lib64/libz.so.1 (0x00007fb537a20000)
libmypaint-1.3.so.0 => ././/lib/libmypaint-1.3.so.0 (0x00007fb53780e000)
libm.so.6 => /lib64/libm.so.6 (0x00007fb537505000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb5372e8000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb536f26000)
libgmodule-2.0.so.0 => ./lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007fb536d21000)
libX11.so.6 => /lib64/libX11.so.6 (0x00007fb5369e1000)
libXfixes.so.3 => ./lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007fb5367db000)
libatk-1.0.so.0 => ./lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007fb5365b8000)
libXrender.so.1 => ./lib/x86_64-linux-gnu/libXrender.so.1 (0x00007fb5363ae000)
libXinerama.so.1 => ./lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007fb5361ab000)
libXi.so.6 => ./lib/x86_64-linux-gnu/libXi.so.6 (0x00007fb535f9a000)
libXrandr.so.2 => ./lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007fb535d90000)
libXcursor.so.1 => ./lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007fb535b85000)
libXcomposite.so.1 => ./lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007fb535982000)
libXdamage.so.1 => ./lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007fb53577f000)
libXext.so.6 => ./lib/x86_64-linux-gnu/libXext.so.6 (0x00007fb53556c000)
libpng16.so.16 => /lib64/libpng16.so.16 (0x00007fb535339000)
libthai.so.0 => ./lib/x86_64-linux-gnu/libthai.so.0 (0x00007fb53512f000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fb534f03000)
libpng12.so.0 => ./lib/x86_64-linux-gnu/libpng12.so.0 (0x00007fb534cdc000)
libgraphite2.so.3 => ./lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007fb534ab6000)
libpixman-1.so.0 => ./lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007fb53480d000)
libxcb-shm.so.0 => ./lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007fb53460a000)
libxcb-render.so.0 => ./lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007fb534400000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x00007fb5341de000)
librt.so.1 => /lib64/librt.so.1 (0x00007fb533fd6000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fb533dd1000)
/lib64/ld-linux-x86-64.so.2 (0x000055ae6b4e5000)
libffi.so.6 => ./lib/x86_64-linux-gnu/libffi.so.6 (0x00007fb533bc9000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fb533956000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fb53372e000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fb533514000)
libexiv2.so.12 => ././/lib/libexiv2.so.12 (0x00007fb5330b3000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fb532d2a000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fb532b13000)
libjson-c.so.2 => ./lib/x86_64-linux-gnu/libjson-c.so.2 (0x00007fb532907000)
libdatrie.so.1 => ./lib/x86_64-linux-gnu/libdatrie.so.1 (0x00007fb532700000)
libXau.so.6 => ./lib/x86_64-linux-gnu/libXau.so.6 (0x00007fb5324fb000)

/tmp/.mount_E5foed/usr/bin/gimp.bin --pdb-compat-mode=on “”

(gimp.bin:12912): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(gimp.bin:12912): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,

(gimp.bin:12912): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(gimp.bin:12912): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,
Gtk-Message: Failed to load module “pk-gtk-module”
Gtk-Message: Failed to load module “canberra-gtk-module”
This is a development version of GIMP. Debug messages may appear here.

(gimp.bin:12912): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,

(pyconsole.py:12932): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(pyconsole.py:12932): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,

(pyconsole.py:12932): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(pyconsole.py:12932): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,
Gtk-Message: Failed to load module “pk-gtk-module”
Gtk-Message: Failed to load module “canberra-gtk-module”

(gimp.bin:12912): LibGimpBase-WARNING **: gimp.bin: gimp_wire_read(): error
GIMP-Error: Unable to run plug-in “gmic_film_cluts.gmz”
(/tmp/.mount_E5foed/usr/lib/gimp/2.0/plug-ins/gmic_film_cluts.gmz)

Failed to execute child process “/tmp/.mount_E5foed/usr/lib/gimp/2.0/plug-ins/gmic_film_cluts.gmz” (Permission denied)

gimp_display_shell_profile_update
gimp_display_shell_profile_update
gimp_display_shell_profile_update
magic match 4 on file-tiff-load
best magic match on file-tiff-load
Unknown field with tag 18246 (0x4746) encountered
Unknown field with tag 18249 (0x4749) encountered

(file-tiff:12943): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(file-tiff:12943): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,

(file-tiff:12943): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(file-tiff:12943): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,
Gtk-Message: Failed to load module “pk-gtk-module”
Gtk-Message: Failed to load module “canberra-gtk-module”

(file-tiff:12943): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,

(file-tiff:12943): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,
Unknown field with tag 18246 (0x4746) encountered
Unknown field with tag 18249 (0x4749) encountered
bps: 32
load_contiguous
bytes_per_pixel: 12, format: 12
file-tiff is updating the progress too often
gimp_display_shell_profile_update
src_profile: sRGB
src_format: R’G’B’A float
dest_format: R’G’B’A float
gimp_display_shell_profile_update
src_profile: sRGB
src_format: R’G’B’A float
dest_format: R’G’B’A float
gimp_display_shell_profile_update
src_profile: sRGB
src_format: R’G’B’A float
dest_format: R’G’B’A float
XXXXXX gimp_image_create_color_transforms XXXXXX

(print:12966): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(print:12966): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,

(print:12966): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(print:12966): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,
Gtk-Message: Failed to load module “pk-gtk-module”
Gtk-Message: Failed to load module “canberra-gtk-module”

(print:12966): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,

(print:12966): Gtk-WARNING **: Unable to locate theme engine in module_path: “pixmap”,
gimp_display_shell_profile_update
[colin@colin Downloads]$

Carmelo_DrRaw · September 29, 2016, 12:20am

Honestly I cannot see any GIMP error message related to printing (and I really need to find a proper way to avoid all the rest of the error messages ).

Have you tried a “standard” GIMP 2.9 installation in the past? Was printing working in that case?

Colin_Adams · September 29, 2016, 6:12am

I’ve not tried 2.9 before.