GIMP AppImage Ignores GIMP3_DIRECTORY Environment Variable - Possible Hardcoding Issue?

[pixelmixer (mark sweeney)]

Hi,

I’m encountering an issue where the GIMP AppImage always runs using the default ~/.config/GIMP/2.99 folder, despite setting the GIMP3_DIRECTORY environment variable to use a custom workspace directory.

Could this behavior be due to this line in the AppImage’s AppRun script? Blame · build/linux/appimage/AppRun · master · GNOME / GIMP · GitLab

From what I understand, it seems like the AppImage might be hardcoded to always use the 2.99 config folder. In my fork, I’ve hardcoded the use of a different config folder to protect user configurations unless a workspace folder is explicitly defined. However, this line might explain why that protection is being overwritten by the default configuration.

Here’s a sample script I’m using to try launching the AppImage with a custom workspace, but it still defaults to the 2.99 folder:

#!/usr/bin/env bash

# This does not launch the GIMP AppImage with a new workspace

# Define the workspace directory
workspace=~/.config/GIMP/testAppImage
mkdir -p "$workspace" 

# Set the GIMP3_DIRECTORY to the workspace
export GIMP3_DIRECTORY="$workspace"

# Launch the AppImage
"$HOME/Desktop/GIMP.AppImage"

[pixelmixer (mark sweeney)]

To confirm, that line does control the AppImage working directory. Building an AppImage with it changed, creates a new .config folder to match.

[brunvonlope (Bruno)]

Thanks for noticing it. Can you test the artifact of gimp-debian-x64 (#4397540) · Jobs · GNOME / GIMP · GitLab and tell me if the bug still persists?

[pixelmixer (mark sweeney)]

Thanks for the fix, the workspace directory is now settable with the GIMP3_DIRECTORY flag.
And thanks for all the AppImage work, it’s a very nice.