Obtain Stack Trace

To find out the cause for troubles in GIMP it’s sometimes necessary to find out some internal information from GIMP. You can get them with the following steps, especially if you are asked for it on Gitlab:

On Windows

  1. Open the Windows command prompt window:

Click start, type cmd. You will see the command prompt appear as the best match. Click on it or hit Enter to open it.

A black window will open - the Windows command prompt window.

  1. For the installer package, enter "%ProgramFiles%\GIMP 3\bin\gimp" --verbose --console-messages. For the Store package, enter gimp-3 --verbose --console-messages

After a moment a black command prompt window will open, having the title ‘GIMP output. You can minimize this window, but don’t close it’. Note that the start might take a bit longer because GIMP now writes output data.

  1. When the GIMP application has started, execute the steps to reproduce the error.

  2. Select the GIMP output and copy it the clipboard: click on the GIMP icon in the upper left window corner, then Edit/Select All, then Edit/Copy.

  3. Open your Internet browser, open your particular bug and paste the message.

On Linux

  1. Open a terminal window.

  2. Enter gimp --verbose --console-messages

Note that the start might take a bit longer because GIMP now writes output data.

  1. When the GIMP application has started, execute the steps to reproduce the error.

  2. Select the GIMP output from the terminal window and copy it the clipboard.

  3. Open your Internet browser, open your particular bug and paste the message.

On Linux with Flatpak

Copy and paste all the commands

flatpak list |grep org.gimp.GIMP

This command returns information about GIMP-related packages.

You need to check where GIMP is installed, as shown in the column Installation. This way you will know whether to install or update in --system or --user.

If a flatpak command asks where to install a component, always choose the same installation target.

You must therefore follow the instructions below depending on the version of GIMP you have installed

For GIMP 3

In all commands, replace --system with --user if GIMP was installed as “user” installation (cf. result of above “list” command).

flatpak install --system flathub org.gimp.GIMP.Debug

FLATPAK_SDK=`flatpak remote-info --system flathub org.gimp.GIMP//stable | grep Sdk: |sed 's/^ *Sdk: *\(.*\)/\1/'`

FLATPAK_SDK_DEBUG=`echo $FLATPAK_SDK | sed 's$\([^/]*\)/\(.*\)$\1.Debug/\2$'`

flatpak install --system flathub $FLATPAK_SDK $FLATPAK_SDK_DEBUG

Then run GIMP with the command 

flatpak run --system --devel org.gimp.GIMP

try to replicate the crash and add the obtained stacktrace to the issue report

For GIMP nightly

In all commands, replace --system with --user if GIMP was installed as “user” installation (cf. result of above “list” command).

flatpak install --system gnome-nightly  org.gimp.GIMP.Debug

flatpak remote-info --system gnome-nightly org.gimp.GIMP//master | grep Sdk: |sed 's/^ *Sdk: *\(.*\)/\1/'

flatpak install --system gnome-nightly org.gnome.Sdk.Debug//master

then run GIMP with the command

flatpak run --system --devel org.gimp.GIMP//nightly

try to replicate the crash and add the obtained stacktrace to the issue report

On MacOS

  1. Go to Applications/Utilities, then Terminal.

  2. Enter /Applications/GIMP.app/Contents/MacOS/gimp --verbose --console-messages Note that the start might take a bit longer because GIMP now writes output data.

  3. When the GIMP application has started, execute the steps to reproduce the error.

  4. Select the GIMP output from the terminal window and copy it the clipboard. In the Mac OS terminal use Edit/Select All, then Edit/Copy.

  5. Open your Internet browser, open your particular bug and paste the message.