Michael Altfield

I disarmed buskill, then I `kill -9`ed the `root_child` process manually. Then I clicked the "arm" button again. ``` 00:47:47,709 packages.buskill DEBUG DEBUG: attempting to disarm BusKill 00:47:47,714 packages.buskill INFO...

> Success! This is important: the user is no longer given a false sense of security by telling them that the `soft-shutdown` trigger is "armed", if that's not the case....

Sigh, of course, in a GUI, this is more complicated than initially expected. The non-root-child process (referenced as `self.usb_handler`) that sits in the background and monitors for usb hotplug events...

all right, I implemented ^ this idea. I tested it, and it appears to be working fine on Linux * https://github.com/BusKill/buskill-app/commit/395cc76547f51b52df3a930fcc26d618e2895ea1 We added a new `usb_handler.status` instance field, which starts-out...

well, the latest build just locks-up the GUI after pressing the "Arm" button. And I didn't even get my debug log prints from inside the while loop, so it looks...

ok, I finally got the exception passing functional between the non-root child process and the main parent process's GUI. Here's what we needed in the end: * https://github.com/buskill/buskill-app/compare/ad12cb2e533644d6e12e1da3f2dcad04346fc01e..0f9fafdf9571d1913cf3f67a1d50a0f4db6a2732

Note: this issue is currently blocked by #87 * https://github.com/BusKill/buskill-app/issues/87 I created a separate issue for resolving the `OSError: dlopen(libusb-1.0.dylib, 6): image not found` bug, which is currently preventing me...

Update: I fixed the `OSError: dlopen(libusb-1.0.dylib, 6): image not found` bug by bumping the libusb tarball from `libusb-1.0.23` to `libusb-1.0.27` in the MacOS build script * https://github.com/BusKill/buskill-app/commit/8a174077834f4f14e17d9286c888acdc56ea0fb8

I think the only thing remaining in this ticket (before testing) is to have the root_child harden its own owner permissions on first execution

This is already done in the CLI. When a USB hotplug event is detected, it will output something like this ``` DEBUG: called hotplugCallbackNix() context:|| device:|Bus 002 Device 002: ID...