ID 351116 - The colorspace of aborted renders is incorrect.

Problem summary
When a render is aborted, the colorspace of the stored image rendered by slave machines is assumed to be RGB instead of linear. This bug can be encountered when network rendering via bug 351001: TP 351001 - A region render using only slave machines does not end the render process when it reaches 100%.

Customer reported version
modo.11.2v1

Customer reported platform
n_a_linux

Steps to reproduce

1) Render a scene file. During the rendering process, abort the render before completion using the Abort button in the Render window.

2) Once aborted, you should notice that the thumbnail for the rendered image in the Render window has been assigned the RGB (FP) colorspace. While the image may appear correct in the UI of the Render window, saving the image locally and viewing it will show the colorspace is incorrect. 

Workaround
Modo will convert the render to the correct colorspace if the rendering process completes correctly. 

Reproduced by support
This bug has been reproduced in:
Windows 10
12.1v1 Beta 6 
12.0v1
11.2v1
10.2v4

macOS
12.1v1 Beta 6
10.2v4

Earliest version tested
10.2v4 - This issue appears to be in all versions of the product.