[quoted lines by Keith Wessel on 2017/03/02 at 08:56 -0600] >I got this by adding -l debug -L /brltty.conf to the args environment var in >the [email protected] that calls the brltty system wrapper.
Unless the above is a typo, it's saying that you're writing the log into brltty's configuration file. >I get as far as brltty starting then, sometimes it tells me screen not in >text mode, and other times it just hangs on the brltty version number on the >braille display. If I even just kill brltty and let system restar it, >everything's fine. It must be starting too early. >Other than the executable args change, my only other >change to the service unit script is to tell it to start after >alsa-restore.service. We had a case where brltty was starting too early, and this is what we now specify: DefaultDependencies=no After=local-fs.target Before=sysinit.target Wants=systemd-udev-settle.service After=systemd-udev-settle.service >Logs are below. That log is indeed vague. Are you able to rebuild your brltty if I send you a patch to one of its source files? -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: [email protected] | Canada K2A 1H7 | http://FamilyRadio.org/ _______________________________________________ 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.com/mailman/listinfo/brltty
