Thirty years after its first public release, GIMP 0.54 is running again on modern Linux thanks to a Flatpak image. This is not an updated or patched version: it is the original from 1996, with its Motif-based interface, brought back to life for code archaeologists and enthusiasts of early free software. No AI, no generative fill or edge detection – we are talking about an image editor that at the time competed with Photoshop by offering clone stamps and destructive deep etching, without layers or masks.

How a Flatpak solves dependency hell

Getting a 1996 binary to run is no trivial task. Current Linux distributions abandoned toolkits like Motif decades ago, and manually rebuilding the required library stack would lead to cascading conflicts and incompatibilities. The project sidestepped the problem by packaging the entire application and its dependencies into a Flatpak container: an isolated runtime that bundles not just the executable but the exact versions of Motif and other components from 1996, enabling GIMP 0.54 to work on x86-64 systems with Wayland without touching the host OS. It’s the same principle as Docker containers applied to the desktop: instead of adapting old software to a new environment, you transport the entire environment along with the application.

The Motif curse and the birth of GTK

Version 0.54 was tied to Motif, the standard X11 graphical toolkit of the 1990s. The problem? Motif was not free software: its FOSS license would not arrive until 2012, after the Common Desktop Environment was open-sourced. This restriction made GIMP distribution difficult and alienated plugin developers. Co-creator Peter Mattis soon grew fed up and wrote his own toolkit, GTK (originally GIMP ToolKit), along with the drawing layer GDK. The move, initially intended as an internal fix, changed Linux desktop history forever: when the GNOME project had to choose a GUI library, it selected GTK over KDE’s Qt, which at the time had a less permissive license. An ecosystem was born that evolved up to GTK 4, while even forks of GTK 1 and 2 are maintained today to support legacy applications like CinePaint.

Legacy software preservation: when containers become strategic for on-premise

The GIMP 0.54 operation is not just a collector’s whim. In the enterprise world, thousands of applications developed in-house or purchased decades ago still run on obsolete stacks, often locked in by dependencies that are no longer updated. Think of document management systems, financial analysis tools, or industrial control panels written with now-extinct toolkits. Re-engineering everything would be costly and risky. That is why containerization techniques like Flatpak – and, in server environments, Docker and Podman – have become a strategic tool for on-premise infrastructure: they encapsulate the entire legacy runtime, isolating it from a modern operating system without rewriting the code. For those evaluating on-premise deployment, clear trade-offs exist: containers add orchestration and updating complexity but ensure the survival of critical software while preserving security through isolation. The GIMP 0.54 Flatpak is a small case study that perfectly illustrates why digital preservation is not optional, but a piece of software lifecycle management in self-hosted environments.

From nostalgia to pragmatism

The fact that we can now launch GIMP 0.54 on an up-to-date system is not a mere historical exercise. It shows that the open-source community has refined tools capable of maintaining not only ideas but also executable bits over the long term. Other vintage toolkits are following similar paths: Tcl/Tk 9 returned after twelve years of silence, FLTK revived after thirteen, and a GTK 1 fork continues to be maintained. The next time your company asks you to resurrect an in-house application written in the nineties, remember that the solution may already be sitting in a Flatpak package.