The can't-fork message builds its flag list from one shared constant; the text is unchanged.
What's wrong with this entry?
The "Can't fork" message no longer hardcodes the list of launch flags that block forking; it interpolates a shared constant, so the enumerated flags are defined once. The visible text about safe or bare mode is unchanged.
Can't fork: this session was started with launch flags (safe or bare mode,
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.