Have the maintainer record the interpreter and imported module paths from the normal launch on each laptop. Compare the installed versions and the documented signature of that read call. Folder names alone will not tell you which copy was loaded.
Have the maintainer confirm the supported combination for that controller and script before changing the argument, then repeat the read from the ordinary shortcut rather than only from an interactive session.
Supported combination confirmed and shortcut corrected. Normal user read returned the expected controller identity. Thanks Victor; imported paths found it.