[BRLTTY] Bug#848008: brltty: fails to detect keyboard when started before systemd-udev-settle.service

[Sebastian Humenda]

Hi

Samuel Thibault schrieb am 13.12.2016,  8:37 +0100:
>Sebastian Humenda, on Tue 13 Dec 2016 06:32:13 +0100, wrote:
>> When enabling a keyboard table in /etc/brltty.conf, brltty should provide
>> navigation commands using the keyboard. On some systems, this doesn't work after
>> boot, because the keyboard has not been detected yet. The fix is to add the
>> following to the unit file:
>> 
>>     [Unit]
>>     After=systemd-udev-settle.service
>>     Wants=systemd-udev-settle.service
>> 
>> This has been fixed upstream, too.
>
>Mmm, but that will delay brltty startup more than strictly necessary.
On my system, the delay is not perceptible, although that is not a objective
measurement.
I have to enter a passphrase for my hard disk and brltty is always up before I
get prompted for it.

>Shouldn't brltty be able to catch keyboard shortcuts from newly-plugged
>keyboards? It'd then just catch the keyboards as they get detected by
>udev, without delaying the startup.
If I understood upstream correctly, that is impossible, because the keyboard is
not detected as new device. New devices are automatically recognized by brltty,
but if udev is still discovering the devices, the handling seems to be
different.

The proposed change possibly breaks the initramfs-option of BRLTTY, but that
never worked for me so far.

Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://mielke.cc/pipermail/brltty/attachments/20161213/9e8df4ef/attachment.sig>