Deep Dive Special : Building a Stable Open-Source Photography Toolkit – The Pitfalls of GIMP 3 and Friends

5 minutes read

Well, it’s been a few weeks since I started the Deep Dive series and published that article on GIMP 3.0 — and let’s just say, it didn’t go unnoticed. I’ve received quite a few responses, mostly via email, a handful in the comments, and they all share one thing: things don’t always work as smoothly as we’d like. And no, there aren’t any magical one-click fixes either. That’s simply because those instant fixes don’t exist.

But maybe, just maybe, you’ll find some answers below — or at least a few nudges in the right direction to help troubleshoot what’s going wrong.

If you’ve recently taken GIMP 3.0 RC2 for a spin and wondered where half your plugins went, you’re not alone. While this shiny new version brings a fresh GTK3 interface and long-overdue Python 3 support, it also breaks quite a few things – especially for photographers who rely on a finely-tuned set of tools. Add Flatpaks, Snaps, and AppImages to the mix, and you’ve got yourself a fun little minefield.

In this Deep Dive, we’ll explore what’s currently working (and what’s not), what to watch out for, and how to stitch together a dependable photo-editing setup without losing your mind. Or your filters.

GIMP 3.0 RC2 – The Good, the Bad, and the Missing Plugins

Yes, it’s faster. Yes, it looks slicker. And no, your favorite plugins from 2017 probably don’t work anymore. That’s because GIMP 3 has officially made the leap to Python 3 and GTK3 – great news for the future, terrible news for your current workflow.

What’s broken (or missing):

• Resynthesizer (bye bye, Heal Selection)
• BIMP
• FX Foundry
• Many older Script-Fu and Python plugins

Some projects are being updated slowly, but the ecosystem hasn’t caught up yet. So unless you enjoy debugging plugin paths and Python traces, maybe don’t rely on GIMP 3.0 as your main editor just yet.

The Container Conundrum: Snap, Flatpak, AppImage

Modern Linux packaging formats like Snap, Flatpak, and AppImage offer a clean and isolated install experience. Unfortunately, they also come with some rather infuriating limitations – especially when apps are supposed to talk to each other.

Common issues include:

• No inter-app communication: GIMP can’t see RawTherapee or Darktable, or vice versa
• Restricted filesystem access: Plugins or LUT folders can be invisible
• Missing dependencies: Especially in AppImages or when launching from desktop icons

For example, Flatpak GIMP may not be able to use system-wide ICC profiles or access /mnt/photos unless you explicitly grant it permission.

G’MIC – Still a Must-Have (If You Can Get It Working)

G’MIC is arguably the most powerful plugin in the GIMP world, and luckily, it still works – with caveats. If you’re using the AppImage version of GIMP 3.0, you’ll need to:

1. Download the G’MIC plugin from https://gmic.eu/download.html
2. Extract and place the binary in:~/.config/GIMP/3.0/plug-ins/
3. Make it executable:chmod +x ~/.config/GIMP/3.0/plug-ins/gmic_gimp_qt

Voilà – Filters > G'MIC-Qt should appear in your menu. Unless it doesn’t. In which case, launch GIMP from the terminal and enjoy the debugging party.

Recommendations: How to Build a Stable Toolkit

If you want your photo-editing apps to cooperate like well-behaved dogs rather than feral cats, here’s what I recommend:

1. Use distro-native installs when possible

Install GIMP, Darktable, and RawTherapee from your Linux distribution’s repositories. It might not be the latest and greatest, but everything generally plays nicer together.

2. Hybrid setup

Run GIMP 2.10 alongside GIMP 3.0 RC2. Use the older version for plugin-heavy tasks and the new one for testing or GTK3-specific needs.

3. If you must use containers…

• Use AppImages for self-contained tools like RawTherapee
• Learn Flatseal if you’re on Flatpak – it gives you control over permissions
• Keep plugins, LUTs, and resources in accessible user folders (~/.config, ~/Pictures/LUTs, etc.)

4. Use stand-alone tools as backups

G’MIC has a stand-alone version. So does RawTherapee. These don’t need GIMP at all and can still do a ton of powerful processing on their own.

When It All Falls Apart: Where to Get Help

Things will break. That’s part of the open-source adventure. But you’re not alone:

• Pixls.us forums – probably the best place for photo-related Linux help
• GIMP GitLab – for reporting (real) bugs
• Reddit r/GIMP – hit or miss, but good for quick sanity checks
• ChatGPT – seriously. If you’re stuck on a weird error, just ask. Something like:

“GIMP 3.0 AppImage doesn’t detect G’MIC plugin – how to fix?”

With enough details, AI can walk you through terminal commands, path checks, and dependency troubleshooting. It’s like having a calm nerdy friend who never sleeps.

Cross-Platform Considerations – What About Windows and macOS?

Let’s not forget the other two-thirds of the world.

Windows

GIMP 3.0 RC2 is available as an installer for Windows, and it suffers from the same plugin compatibility issues – but:

• It’s easier to install G’MIC and other plugins because there’s no sandboxing.
• Communication between apps (like sending RAWs from Darktable to GIMP) generally works out of the box.
• Path issues are usually more manageable.

The catch? Many plugins haven’t been recompiled for the Windows version of GIMP 3 yet. So even if the architecture allows it, they just don’t exist (yet).

macOS

GIMP 3.0 for macOS is still lagging behind a bit. The builds are less frequent, and plugin support is even more limited:

• G’MIC for macOS is hit-or-miss
• Permissions and app sandboxing can block access to resources (like LUT folders or RAW editors)
• Tools like Darktable do work, but exporting to GIMP isn’t always smooth

In short: Windows users have fewer structural barriers, but still face missing plugins. Mac users often need to dig deeper to get things running.

Conclusion: Don’t Panic (but Don’t Rush Either)

GIMP 3 is the future, but it’s not quite your future yet – at least not for serious photography work. For now, a carefully mixed setup of stable, older versions and modern standalone tools is often the best recipe. Avoid the bleeding edge unless you’re okay with getting cut.

And if all else fails? Grab a coffee, launch RawTherapee, and remind yourself: Open Source is a journey – not a shortcut 🙂

Marc.