06.12.2020 23:08, Alexander Epaneshnikov пишет:
06.12.2020 22:49, Dave Mielke пишет:
[quoted lines by Jason White on 2020/12/06 at 13:48 -0500]
Your udev rules look good. Is the kernel log showing a USB disconnect?
Apparently not. Here are the logs created by reconnecting the device
while
running systemctl -f.
i'm mystified, especially because you and Alexander are using the
same version
of systemd. I think you said earlier that all this started happening
when you
upgraded systemd. Is that right?
The natyure of the problem is that the brltty service instance that's
controllibng your device stays active as long as it's required, i.e.
(in this
case) as long as the virtually created device unit depends on it. It
seems that
this dependency isn't being maintained on your system, which, to me,
is just
plain wrong.
Could you please attach the output of systemctl list-units?
don't worry Dave, i am mystified too. especially when i rebootied with
udev debug enabled and all is working nicely.
i attach file when all is working.
very strange, but if I add a |udev.log-priority=debug| to the kernel
parameters
all is working. if i remove it. brltty is stops.
if i list units among them will not be brltty.
--
Sincerely, Alexander.
_______________________________________________
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
