I think the usb rules are being executed, the problem seems to be with the [email protected]. I am not sure why its not working, it claims it can't execute /libexec/brltty/systemd-wrapper, but I can do it manually, so I have no clue.
On Mon, 22 Feb 2021 01:44:03 -0500, Didier Spaier wrote: > > Because simple is not funny, John :D > > As an aside I have also an issue with 6.3 in Slint, people can't > get brl through > orca at boot, they have to first kill the daemon with a signal 9 (15 doesn't > work). I have a power user testing to investigate further right now (I am > sighted, do not read Braille and don't have display anyway). Not > using systemd > in Slint so could be a completely unrelated issue though. But i > suspect USB is > involved as if I start brltty -b tt -d /dev/tty2 I do get the > expected output > in /dev/tty2. > > Best, > Didier > > Le 22/02/2021 à 07:18, John Covici a écrit : > > A bit more information, both pcspkr and uinput are loaded, so I don't > > know why those modprobes are failing and unplugging and replugging the > > braille device does not do anything. > > > > I think it keeps trying to start a braille device instance, but its > > always failing, not sure why. It seems to be unable to execute > > /libexec/brltty/systemdd-wrapper, but its there. Very strange. Why > > is this so complicated? > > > > > > On Sun, 21 Feb 2021 22:35:18 -0500, > > Dave Mielke wrote: > >> > >> [quoted lines by John Covici on 2021/02/21 at 15:58 -0500] > >> > >>> Also, looking at the only service unit, it says RefuseManualStart=true > >>> so I seem to have no way to just say systemctl start brltty > >> > >> Okay, I understand your question, now. If you really want to just start > >> brltty > >> then start the brltty.path unit. > >> > >> Just starting brltty, these days, isn't necessarily the right thing to do. > >> This > >> is because udev also starts brltty. If you don't have brltty's udev rules > >> then > >> just starting brltty is okay. If, however, you do have them then you should > >> configure the general brltty to not look for USB devices. An easy way to do > >> this would be to have this line in brltty.conf: > >> > >> braille-device bluetooth: > >> > >> By the way: It's often handy to check the description within a systemd unit > >> file. The brltty.path unit contains this line: > >> > >> Description=Default BRLTTY Instance > >> > >> -- > >> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ > >> Dave Mielke | 2213 Fox Crescent | WebHome: http://Mielke.cc/ > >> EMail: [email protected] | Ottawa, Ontario | Twitter: @Dave_Mielke > >> Phone: +1 613 726 0014 | Canada K2A 1H7 | > >> > > > _______________________________________________ > 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 > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una [email protected] _______________________________________________ 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
