The logs suggest that BRLTTY was started and then immediately shut down
during boot, but I don't know why. Of course, the new systemd may not be
responsible, but the emergence of the problem did correspond to the
upgrade to systemd 247.1.
I've also read an LWN article on the systemd backward-incompatible
changes, but I didn't find anything obviously suspect in the BRLTTY udev
rules.
On 12/3/20 7:40 PM, Jason White wrote:
On 12/3/20 7:13 PM, Alexander Epaneshnikov wrote:
can't reproduce. can you send output of:
~ journalctl [email protected] -b0
--no-pager --no-hostname
Here's the output.
-- Journal begins at Sat 2019-01-26 15:51:19 EST, ends at Thu
2020-12-03 19:36:37 EST. --
Dec 03 19:35:35 systemd[1]: Starting BRLTTY Instance:
/dev/bus/usb/001/002...
Dec 03 19:35:35 brltty[523]: BRLTTY 6.1 rev unknown [http://brltty.app/]
Dec 03 19:35:35 systemd-wrapper[523]: BRLTTY 6.1 rev unknown
[http://brltty.app/]
Dec 03 19:35:35 systemd-wrapper[523]: brltty: directory created:
/run/brltty
Dec 03 19:35:35 brltty[523]: directory created: /run/brltty
Dec 03 19:35:35 brltty[523]: BrlAPI Server: release 0.8.0
Dec 03 19:35:35 systemd-wrapper[523]: brltty: BrlAPI Server: release
0.8.0
Dec 03 19:35:35 systemd[1]: Started BRLTTY Instance:
/dev/bus/usb/001/002.
Dec 03 19:35:35 systemd[1]: Stopping BRLTTY Instance:
/dev/bus/usb/001/002...
Dec 03 19:35:35 systemd[1]: [email protected]:
Succeeded.
Dec 03 19:35:35 systemd[1]: Stopped BRLTTY Instance:
/dev/bus/usb/001/002.
_______________________________________________
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
