I think I've got something working for #8. I was having to unplug / plug in the keyboard to get it working after reboot or power cycle. But with this it picks it up on startup! I was excited anyway.
It changes up things a bit though and the service bypasses sort-and-run.sh which could be cleaned up if you're good with the approach in this PR. Also it runs two separate instances of kfreestyle2d, one for each device. You can get the status with systemctl status kfreestyle2d@kinesis1.service for example. AFAIK two instances are fine?
Changes:
Udev uses the systemd tag and SYSTEMD_WANTS to kick off the service
Here's a good example of putting it all together. It's also where I got the idea to depend on user session service. (edit: works fine without waiting for systemd-user-sessions.service)
I think I've got something working for #8. I was having to unplug / plug in the keyboard to get it working after reboot or power cycle. But with this it picks it up on startup! I was excited anyway.
It changes up things a bit though and the service bypasses
sort-and-run.sh
which could be cleaned up if you're good with the approach in this PR. Also it runs two separate instances ofkfreestyle2d
, one for each device. You can get the status withsystemctl status kfreestyle2d@kinesis1.service
for example. AFAIK two instances are fine?Changes:
systemd
tag andSYSTEMD_WANTS
to kick off the serviceHere's a good example of putting it all together. It's also where I got the idea to depend on user session service. (edit: works fine without waiting for
systemd-user-sessions.service
)