"Failed to execute script main"

[fitnesskingen]

Describe the bug
I installed the software for my Buskill on a windwos computer. I updated the software inside the app, just like recommended on buskill website. I updated the the app because i wanted to change the User Interface so i can close my computer when the buskill is triggered and not only lock my screen. The update seems not to work.

To Reproduce
Plug the buskill in to your computer. Drag the buskill for windows map to your desktop. Update the app. After update it will say 👍
"Failed to execute script main"

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Versions (please complete the following information):

• OS: [e.g. Windows 10]
• BusKill: [e.g. v0.2.0]

Additional context
For me it is important that the computer shuts down when the buskill is triggered and not only lock my screen. A screen lock is easily brut forced even if the computer hard drive is encrypted.

[fitnesskingen]

why i wanted to update the app in the first place is because i the menu in the app it was missing the settings feature. Like the one on the picture from Buskills official website. See picture

[maltfield]

Thanks for the report.

What version of Windows are you running?

Can you please copy and paste the output of the Debug Log to this ticket immediately after the error appears?

• https://docs.buskill.in/buskill-app/en/stable/support.html#bug-reports

[fitnesskingen]

I am running Windows 10. i dont have a debug log since i deleted the app and made my own script. But it would be nice to have the app and to be able to choose between different features.

[fitnesskingen]

I have another issue as well. It would be awesome to be able to ignore short disconnects since the kable seems to trigger a hard shutdown by itself.

cheers

[maltfield]

I have another issue as well. It would be awesome to be able to ignore short disconnects since the kable seems to trigger a hard shutdown by itself.

@fitnesskingen the only software solution I can think of (as opposed to learning how to sit with the BusKill magnetic disconnect rested on your lap in such a way that physically minimizes false positives) would be to delay the trigger by maybe 10 seconds, and only trigger if it wasn't re-plugged-in during that time.

Would you still be interested in this new "ignore short disconnects" feature, if it meant there would be a delay of the trigger of 10-20 seconds?