GIMP AppImage (continuous integration)

Software GIMP
49

Setting permissions for all neither requires sudo nor does it impose the slightest safety or security difference. Just saying …

50

You’re right, and:

sdfkjhgsdfkjhgsdf20chars

51

I will add this option to the gimp invocation. I personally prefer this solution instead of manually patching the plug-in scripts…

Thanks for the hint!

52

And a+x is what the AppImage project recommends.

53

Here is a new version of the appimage: Dropbox - gimp-2.9.5-20160823.glibc2.15-x86_64.AppImage - Simplify your life

It now accepts image file names as parameters, to it can be used as a command to directly open an image from the terminal.

2 Likes
54

There was some discussion about better desktop integration on another thread, that I’m linking here for completeness: Gimp + PhF appimage, a few observations - #11 by paperdigits

55

I’ve tested the AppImage desktop integration and it seems to work quite well.

When enabled, the desktop integration will

  • put an entry in the applications menu, called “GIMP AppImage”
  • add an entry in the “Open with…” context menu of most common file managers
  • let you select the appimage as the default program associated to image files

To test this new functionality, you need to:

New versions of the appimage will automatically detect the presence of an old .desktop file and they will prompt you for installing a new one when needed.

@paperdigits and @Fotonut might be particularly interested by this new functionalities…

EDIT: the only issue I’ve encountered so far is that when running the appimage from the applications menu, GIMP complains with this error message: “Opening ‘/tmp/.mount_2CANTA/usr/%U’ failed: Error opening file: No such file or directory”. It is harmless but a bit annoying, and I have no idea how to get rid of it…

2 Likes
56

Hey @Carmelo_DrRaw, how can one add the plugin registry to the appimage? is that something I can do, or would that need to be included as part of the appimage?

Cheers.

57

Are you able to define Plug-In and Scripts folders in the GIMP preferences?

58

Yes, and both are working fine. I have already downloaded some plugins from http://registry.gimp.org/glossary/a, and they seem to be working fine.

What I was hoping to do was use the ‘gimp-registry-plugins’ from the repos. Is this possible to do with an appimage, and if so, how?

Cheers.

59

Hi Brian,

I am a bit reluctant to include a lot of potentially not useful plugins in the appimage, so the best would be to select those that are really relevant for photography purposes.

Anyhow, the appimage looks for additional plugins in this folder:

$HOME/.config/GIMP-AppImage/2.9/plug-ins

For python plug-ins it should be enough to copy them there, on the other hand compiled C/C++ plug-ins might not work and would need to be included in the appimage… one needs to experiment a bit.

If you have suggestions for must-have plugins, I’ll be glad to add them to the appimage package.

Thanks!

1 Like
60

The gimp-plugin-registry deb package installs all its files in the /user file system.

Not possible with an appimage which creates a temporary file system.

You put these files manually in the Gimp 2.9 appimage Gimp profile
~/.config/GIMP-AppImage/2.9/plug-ins/ and ~/.config/GIMP-AppImage/2.9/scripts/

How to get the files? Download the appropriate 64 bit deb file and unpack it.

To save a lot of user confusion I have done it for you and split into scripts and plugins

Now you have to ask yourself, do I really need all 165 scripts and 25 plugins?

Pick what you need but do not expect all to work with this appimage. Turning on pdb-compatibility is largely cosmetic, you just do not see the warning messages. Some, such as separate+ , layer-fx.py (in the scripts???) do not work and AFAIK cmyk-tiff-2-cmyk-pdf.py has never worked since Gimp 2.6

hope this helps.

61

Thanks @rich2005, this will be a great help!

EDIT: I’ve tried a few from the above scripts and pligins, and all work wonderfully. None of the last ones you mention though, I didn’t try them.

62

Just out of curiosity, is there any way I can avoid this? Usually I just click ‘Page 1’ and then import, but to have it not appear at all, and still open as expected would be much better. It happens in regular Gimp too.

Thanks in advance.

63

Those are layers in your tiff file, what if at some point you need layers?

64

I see. So how would they have been created? I always merge down layers before exporting.

Whenever I open a tiff that I have worked on, I get this box appear. When I click ‘select all’, I get a blank canvas and a number of errors show, but selecting ‘Page 1’ gives me the image I last worked on, usually with no error box.

So I think I’m not understanding something…

65

Wait, you are using TIFF as an intermediate file format while working in GIMP? You should really consider using XCF for that.

66

I have changed the title of the topic since I think the AppImage is now ready for a wider testing.

The link in the “Community-built Software” now points to a package hosted in the pixls.us/files area.
Announcements about new features and bug reports related to the GIMP appimage should be posted in this thread, so that they can easily be tracked.

Next addition to the appimage will be the amazing “liquid rescale” plug-in!

1 Like
67

The inclusion of the Liquid Rescale plug-in was straightforward, and it works like a charm!

An updated GIMP AppImage including liquid rescale is ready for download from the “Community Software” page.

Happy editing!

2 Likes
68

[quote=“Carmelo_DrRaw, post:14, topic:1959”]
I think this an unavoidable price to pay… as far as i understand it, the appimage is a compressed disk image. Each time it is launched the system needs to uncompressed the image and mount it via a loop back device. [/quote]

Yes, but what is slowing down the GIMP start is that GIMP re-scans for plugins each time the location of the plugins changes, which it does every time the AppImage is mounted. Discussing this with GIMP developers right now.