In summary, this issue is a result of inconsistent environments that Windows uses between 32-bit and 64-bit applications.
A simple way to call "Bubbles.scr" screensaver directly from Shutter is via the Run Program action with the following path:
C:\Windows\Sysnative\Bubbles.scr /S
Alternatively, if you wish to use environment variables, you can call it as follows:
cmd.exe /C %SystemRoot%\Sysnative\Bubbles.scr /S
You can find more background information on the underlying issue here:
"Msg" command not executable from Batch script
So I found out that if I run the bubbles.scr as an executable, it still works as expected, and I decided to use Shutter's functionality to start it on user idle event.
The problem is that if I set Shutter to execute %systemroot%\system32\bubbles.scr /s, it shows an error:
Error: Failed to execute %systemroot%\system32\bubbles.scr /s : 2
I've tried executing it without the /s parameter, and also from a .bat script wrapper. The only difference was in the latter case - no error was shown (Status = "Finished"), but also no screensaver started.
Any idea what could the problem be?
]]>