Thanks, TerryN. Renamed ~/.openshot & added #!/bin/sh in /usr/bin/blender and all is well again
I've been meaning to ask about this ... OK I'm a bit daft and I should just first try it but this is bugging me. /usr/bin/blender is a binary file. I'm sure it can be edited with a text editor.
When you mean add #! /bin/sh at the top of the file, did you mean it literally? Wouldn't that mess up the blender (the executable)? Wouldn't it be the same as calling the executable with a bash script that included #! /bin/bash?
No, it is not a binary executable it is a shell script wrapper!
And you are right Archie, editing a binary file will corrupt the same.
BTW, the real executables are /usr/bin/blender.sse and /usr/bin/blender.nonsse, the shell script wrapper select one or the other depending if the CPU support sse or not.
Thanks for the explanation, AS. I would have thought it was the binary when I opened it (I can't remember how long ago) and saw nothing but jibberish text, symbols and numbers.
Are the devs at Blender aware of this workaround with Openshot? I guess the Openshot devs already know about this.
Anyway, I learned something new again today ... shell script wrapper ... and it don't look anything like a shell script.