I have a hack in place. /etc/udev/rules.d/99-brltty.rules SUBSYSTEM=="tty", KERNEL=="tty[0-9]*|hvc[0-9]*|sclp_line[0-9]*|ttysclp[0-9]*|3270/tty[0-9]*", GROUP="tty", MODE="0620" Then udevadm control --reload-rules && udevadm trigger This fixed all the problems. ----- Original Message ----- From: Aura Kelloniemi <[email protected]> To: "Informal discussion between users and developers of BRLTTY." <[email protected]> Date: Wed, 12 Nov 2025 12:28:29 +0200 Subject: Re: [BRLTTY] BRLTTY appears severely broken
> Hi Rob, > > On 2025-11-12 at 03:42 -0600, "Rob Hudson" <[email protected]> wrote: > > I added those lines to the brltty.conf file. Unplugged my display. Killed > all brltty processes. Replugged the display and tried to get into a console. > Unplugged display, re-killed all processes. No log file was created. The path > I used was /var/log/brltty.log > > BRLTTY cannot write to /var/log as it is running under an unprivileged user. > You need to put the log file to /tmp/ or some other directory where the > `brltty` user has write permissions. > > Your original problem, by the way, most likely is that BRLTTY does not have > access to /dev/tty0. It is a permissions problem. > > As far as I understand, Arch has not changed anyghing, it is Linux kernel > itself that has changed default permissions of /dev/tty devices. > > You can try running your Arch with linux-lts kernel package to try to confirm > my theory. > > There is a fix already in BRLTTY's git repository. It fixes this. > > -- > Aura > _______________________________________________ > 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 > _______________________________________________ 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
