[BRLTTY] Are changes needed for systemd 247.1?

[Alexander Epaneshnikov]

05.12.2020 21:57, Jason White пишет:
>
> On 12/5/20 1:32 PM, Alexander Epaneshnikov wrote:
>> yep i see. can you provide your display model and it would also be 
>> nice to know the dmesg output also what happens if you reconnect your 
>> display while arch is running?
>>
> It's a Freedom Scientific Focus 80 display connected via USB. here's 
> the result of reconnecting the device:
>
> Dec 05 13:48:40 jpw kernel: usb 1-5: new full-speed USB device number 
> 9 using xhci_hcd
> Dec 05 13:48:40 jpw kernel: usb 1-5: New USB device found, 
> idVendor=0f4e, idProduct=0112, bcdDevice= 3.00
> Dec 05 13:48:40 jpw kernel: usb 1-5: New USB device strings: Mfr=1, 
> Product=2, SerialNumber=0
> Dec 05 13:48:40 jpw kernel: usb 1-5: Product: Focus 2
> Dec 05 13:48:40 jpw kernel: usb 1-5: Manufacturer: Freedom Scientific
> Dec 05 13:48:40 jpw mtp-probe[11664]: checking bus 1, device 9: 
> "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5"
> Dec 05 13:48:40 jpw mtp-probe[11664]: bus: 1, device: 9 was not an MTP 
> device
> Dec 05 13:48:40 jpw systemd[1]: Invalid unit name 
> "brltty@/dev/bus/usb/001/009.service" escaped as 
> "brltty at -dev-bus-usb-001-009.service" (maybe you should use 
> systemd-escape?).
> Dec 05 13:48:40 jpw systemd[1]: Starting BRLTTY Instance: 
> /dev/bus/usb/001/009...
> Dec 05 13:48:40 jpw mtp-probe[11668]: checking bus 1, device 9: 
> "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5"
> Dec 05 13:48:40 jpw mtp-probe[11668]: bus: 1, device: 9 was not an MTP 
> device
> Dec 05 13:48:40 jpw systemd-wrapper[11676]: starting executable: 
> brltty -E -n
> Dec 05 13:48:40 jpw brltty[11667]: BRLTTY 6.1 rev unknown 
> [http://brltty.app/]
> Dec 05 13:48:40 jpw systemd-wrapper[11667]: BRLTTY 6.1 rev unknown 
> [http://brltty.app/]
> Dec 05 13:48:40 jpw brltty[11667]: BrlAPI Server: release 0.8.0
> Dec 05 13:48:40 jpw systemd-wrapper[11667]: brltty: BrlAPI Server: 
> release 0.8.0
> Dec 05 13:48:40 jpw systemd[1]: Started BRLTTY Instance: 
> /dev/bus/usb/001/009.
> Dec 05 13:48:40 jpw audit[1]: SERVICE_START pid=1 uid=0 
> auid=4294967295 ses=4294967295 msg='unit=brltty at -dev-bus-usb-001-009 
> comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? 
> terminal=? res=success'
> Dec 05 13:48:40 jpw systemd[1]: Stopping BRLTTY Instance: 
> /dev/bus/usb/001/009...
> Dec 05 13:48:40 jpw kernel: audit: type=1130 
> audit(1607194120.569:166): pid=1 uid=0 auid=4294967295 ses=4294967295 
> msg='unit=brltty at -dev-bus-usb-001-009 comm="systemd" 
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Dec 05 13:48:40 jpw systemd[1]: brltty at -dev-bus-usb-001-009.service: 
> Succeeded.
> Dec 05 13:48:40 jpw systemd[1]: Stopped BRLTTY Instance: 
> /dev/bus/usb/001/009.
> Dec 05 13:48:40 jpw audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
> ses=4294967295 msg='unit=brltty at -dev-bus-usb-001-009 comm="systemd" 
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Dec 05 13:48:40 jpw kernel: audit: type=1131 
> audit(1607194120.576:167): pid=1 uid=0 auid=4294967295 ses=4294967295 
> msg='unit=brltty at -dev-bus-usb-001-009 comm="systemd" 
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
>

hmmm. looks odd. i use the same display as you.
you need to somehow enable brltty logs. Dave should know better, but i 
suggest to modify systemd-wrapper file.

-- 
Sincerely, Alexander.