Failing to fork work into the background may show a fixed message instead of the real error.
What's wrong with this entry?
When the confirm dialog for forking work into the background fails to start the session, some connections now show a fixed message instead of the underlying error text.
- The message is "Couldn't start the background session (detail withheld on this connection)."
- Which connections redact is decided by a check on the connection type; the helper behind that check is not resolved in this build.
Couldn't start the background session (detail withheld on this connection).
Strings lifted out of the shipped bundle, so the claim above can be checked against them.