Nathaniel van Diepen

Not offhand, it was one of the earlier 3.x versions I believe. A version check doesn't make too much sense in the package, in reality we need to better support...

> I just want to note that, when I installed the ipk from the build artifact, in the `keyd.service`, the expected line for ExecStart is `/opt/bin/keyd`. However, when I installed...

I haven't looked too closely, but if there is a keyd.service file in the source that's overwriting the one included in the package folder, changing the order you install the...

> In this particular case having a separate keyd.service is not needed: it suffices to add `PREFIX=/opt/` to the build environment A tiny bit more than that was required to...

> This is still not working: the binary is `/opt/bin/keyd` but the service calls `/opt/usr/bin/keyd`. I think you are over engineering it a little, setting `PREFIX` should take care of...

> > The latest code does, but we are dealing with the [v2.4.3 tag](https://github.com/rvaiya/keyd/tree/v2.4.3) which is missing some build process fixes. > > This is annoying It is :laughing: ,...

For future reference when we get here, I think this is a good/sane default for the US layout. It at least makes the legends match what the keyboard actually outputs,...

> Keyd seems to freak out on boot and has key-repeats even when the key is clicked once.. I have to restart the service to fix it I haven't experienced...

Have you checked the keyd logs to see if it has anything useful? It works by grabbing all other physical keyboard input and creating it's own evdev device with uinput...

> Upon installation, it instructed me to disable the shutdown target, which seems not relevant. What launcher are you using? And what is the output of `toltecctl status`? > I...