We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
● jelling.service - Jelling BTLE OTP Receiver daemon Loaded: loaded (/lib/systemd/system/jelling.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2018-09-25 11:07:50 EDT; 1min 57s ago Process: 25446 ExecStart=/usr/local/libexec/jelling (code=exited, status=1/FAILURE) Main PID: 25446 (code=exited, status=1/FAILURE)
Sep 25 11:07:50 zorro systemd[1]: Started Jelling BTLE OTP Receiver daemon. Sep 25 11:07:50 zorro jelling[25446]: /usr/local/libexec/jelling: Error opening (null): Bad address
The text was updated successfully, but these errors were encountered:
mention CONFIG_INPUT_UINPUT=y in README.md
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
● jelling.service - Jelling BTLE OTP Receiver daemon
Loaded: loaded (/lib/systemd/system/jelling.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-09-25 11:07:50 EDT; 1min 57s ago
Process: 25446 ExecStart=/usr/local/libexec/jelling (code=exited, status=1/FAILURE)
Main PID: 25446 (code=exited, status=1/FAILURE)
Sep 25 11:07:50 zorro systemd[1]: Started Jelling BTLE OTP Receiver daemon.
Sep 25 11:07:50 zorro jelling[25446]: /usr/local/libexec/jelling: Error opening (null): Bad address
The text was updated successfully, but these errors were encountered: