brltty.service: Failed at step SECCOMP spawning /bin/sh: Invalid argument

Bug #1654546 reported by sam tygier on 2017-01-06
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu Pi Flavour Maker
Undecided
Unassigned
brltty (Ubuntu)
Undecided
Unassigned

Bug Description

I get this logged in the journal every 30 seconds. Running Ubuntu Mate 16.04 on a raspberr pi2.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: brltty 5.3.1-2ubuntu2.1
Uname: Linux 4.1.19-v7+ armv7l
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: armhf
CurrentDesktop: MATE
Date: Fri Jan 6 12:13:12 2017
SourcePackage: brltty
UpgradeStatus: No upgrade log present (probably fresh install)

sam tygier (samtygier) wrote :

Firstly, it does not look like you are using the official raspberry pi kernel for Xenial. Your kernel is 4.1, and the Xenial kernel is 4.4, so it is possible that the kernel you are using does not have the required apparmor bits that Ubuntu needs.

As for the error, does journalctl contain any more information WRT brltty, and does systemctl status brltty also contain any more information?

sam tygier (samtygier) wrote :

Yes, I am using xenial 16.04 (I made a typo in the description). So its because the raspberrypi version ships with an older 4.1.19-v7 kernel in the package raspberrypi-bootloader i think.

description: updated
sam tygier (samtygier) wrote :

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'.

sam tygier (samtygier) wrote :

Still an issue with the 4.4.38-v7+ kernel that recently arrived in Ubuntu MATE 16.04

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in brltty (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers