Got another report of this issue, so maybe it's not caused by user action after all, tentatively marking this bug as a duplicate of the other.
Got another report of this issue, so maybe it's not caused by user action after all, tentatively marking this bug as a duplicate of the other.