Keep a GNOME Terminal Window Open After a Custom Command Exits
A GNOME Terminal profile can run a custom command and close as soon as that command exits. A brief flash of a window may therefore hide a useful success or error message. Preserve the next result by changing the profile's exit behaviour, after checking whether another run is appropriate.
Identify the profile and command
Open GNOME Terminal through a working normal profile and inspect Preferences. Select the profile used by the affected launcher. Check its Command settings and record the custom command privately. A launcher may use a different profile from the one you normally see.
Before repeating the command, establish what it does and whether the previous attempt may already have succeeded. A closed window does not prove failure. Commands that submit jobs, move files or change data need their resulting state checked before being run again.
Where possible, clone the affected profile and give the copy a recognisable diagnostic name. GNOME documents that a clone can be adjusted without changing the original profile. Keep a normal working profile available while testing custom startup behaviour.
Hold the completed result
In the diagnostic profile's Command settings, change When command exits to Hold the terminal open. The alternatives include exiting the terminal and restarting the command; the latter is unsuitable when the goal is to inspect one completed attempt. Preferences are saved as you select them.
Launch the documented harmless test or the justified next attempt through that profile. When the command exits, read the retained output and note its final result. Holding a terminal window open does not keep the finished program running or turn its result into a success.
Copy the relevant output into a reviewed support note, preserving error punctuation and removing private values. Once the issue is understood, retain or remove the diagnostic profile deliberately. Verify that the normal terminal still opens a usable shell and that the production launcher has the intended behaviour.
Sources: GNOME documentation, GNOME documentation.