As we've discussed, I set up a systemd unit to run BRLTTY under my user
identity to provide access to the terminal in Wayland sessions (with
Orca's taking care of the desktop).
This was working well until I upgraded to the latest version of BRLTTY
from Git, via the Arch Linux brltty-git package - see the log messages
below. BRLTTY terminates and does not monitor the terminal.
Is there something wrong with my system configuration?
Jun 29 11:37:21 jpw brltty[1384]: group not joined: 965(pulse-access)
Jun 29 11:37:21 jpw brltty[1384]: brltty: group not joined:
965(pulse-access)
Jun 29 11:37:21 jpw brltty[1384]: group not joined: 987(uucp)
Jun 29 11:37:21 jpw brltty[1384]: brltty: group not joined: 987(uucp)
Jun 29 11:37:21 jpw brltty[1384]: brltty: required capability not
granted: cap_sys_admin (for injecting input characters typed on a
braille device)
Jun 29 11:37:21 jpw brltty[1384]: brltty: required capability not
granted: cap_sys_tty_config (for playing alert tunes via the built-in PC
speaker)
Jun 29 11:37:21 jpw brltty[1384]: brltty: required capability not
granted: cap_mknod (for creating needed but missing special device files)
Jun 29 11:37:21 jpw brltty[1384]: required capability not granted:
cap_sys_admin (for injecting input characters typed on a braille device)
Jun 29 11:37:21 jpw brltty[1384]: required capability not granted:
cap_sys_tty_config (for playing alert tunes via the built-in PC speaker)
Jun 29 11:37:21 jpw brltty[1384]: required capability not granted:
cap_mknod (for creating needed but missing special device files)
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://brltty.app/mailman/listinfo/brltty
