Problem summary: System Restarts are not interrupted when the current Nuke script has unsaved changes
This issue appears to be specific to Windows and Linux devices.
Customer reported version: Nuke 15.0
Customer reported platform: Rocky 9
Steps to reproduce: 1) Launch Nuke and create a Grade node in the Node Graph 2) Restart the machine via the Operating System's UI, by navigating to Start > Power > Restart for example 3) Observe how the Restart proceeds without prompting the user to save their changes in Nuke.
Expected behavior: When the current .nk Nuke script has unsaved changes, Nuke should interrupt any System Restart processes as it does on macOS.
Actual behavior: If a Nuke script with unsaved modifications is open and a System Restart is triggered, Nuke will not interrupt the Restart and the user will not have the option to save their changes.
Prior to 16.0v1, restarting a Rocky Linux device would prompt the user to save their Nuke script changes, but the dialog window would appear in the background and not actually interrupt or affect the reboot process:
Prior to 16.0v1, restarting a Windows device with unsaved changes in Nuke would interrupt the restart and allow the user to save their changes:
Workaround: No known workaround at this time.
Reproduced by Support in: Nuke 16.0v6 - Windows 11, Rocky 9 Nuke 16.0v1 - Windows 11, Rocky 9 -- Windows Regression Nuke 15.2v6 - Rocky 9
