In the logs I just get these repeated over
$ sudo journalctl -u brltty.service --since=today
-- Logs begin at Fri 2017-01-06 06:48:58 GMT, end at Tue 2017-01-10 14:47:03
GMT. --
Jan 10 14:45:27 sampi systemd[1]: Started Braille Device Support.
Jan 10 14:45:27 sampi systemd[16953]: brltty.service: Failed at step SECCOMP
spawning /bin/sh: Invalid argument
Jan 10 14:45:27 sampi systemd[1]: brltty.service: Main process exited,
code=exited, status=228/SECCOMP
Jan 10 14:45:27 sampi systemd[1]: brltty.service: Unit entered failed state.
Jan 10 14:45:27 sampi systemd[1]: brltty.service: Failed with result
'exit-code'.
Jan 10 14:45:57 sampi systemd[1]: brltty.service: Service hold-off time over,
scheduling restart.
Jan 10 14:45:57 sampi systemd[1]: Stopped Braille Device Support.
Jan 10 14:45:57 sampi systemd[1]: Started Braille Device Support.
$ sudo systemctl status brltty.service
● brltty.service - Braille Device Support
Loaded: loaded (/lib/systemd/system/brltty.service; enabled; vendor preset:
enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2017-01-10
14:47:58 GMT; 8s ago
Docs: man:brltty(1)
http://brltty.com/
Process: 17251 ExecStart=/bin/sh -c grep -sq '^ *RUN_BRLTTY=no'
/etc/default/brltty || exec /sbin/brltty -P /run/brltty.pid (
Main PID: 17251 (code=exited, status=228/SECCOMP)
Jan 10 14:47:58 sampi systemd[1]: brltty.service: Main process exited,
code=exited, status=228/SECCOMP
Jan 10 14:47:58 sampi systemd[1]: brltty.service: Unit entered failed state.
Jan 10 14:47:58 sampi systemd[1]: brltty.service: Failed with result
'exit-code'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654546
Title:
brltty.service: Failed at step SECCOMP spawning /bin/sh: Invalid
argument
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pi-flavour-maker/+bug/1654546/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
