07.12.2020 23:33, Dave Mielke пишет:
[quoted lines by Alexander Epaneshnikov on 2020/12/07 at 21:47 +0300]
this doesn't made any difference.
Maybe this one shouldn't hold up 6.2, then. In the end, it's a time bomb just
waiting to strike. :-( We really need the systemd people to help us figure this
one out.
maybe. can you do a point release when it's fixed? i will write to
systemd list tomorrow will try my best to explain hour situation.
How hard would it be to figure out exactly which systemd broke it?
I will try to downgrade systemd to 246 and see.
i am thinking should we try to add implecete dependency on device-unit to
[email protected].
The problem is that we can't add stuff to the device unit as it's virtual.
yep. already understood that.
i tried: BindsTo=%I After=%I
I think we need one that works the other way around. Maybe try PatOf.
nevertheless, there's still a problem. The controlling unit could be a path or
a device unit, and we don't know which one it is.
when the display is connected i see this:
[alex@alex-pc ~]$ systemctl status dev-bus-usb-001-008.device
● dev-bus-usb-001-008.device - Focus_2
Follow: unit currently follows state of
sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d6.device
Loaded: loaded
Active: active (plugged) since Mon 2020-12-07 23:36:06 MSK; 11min ago
Device: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-6
what's strange, if i ask status of
sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d6.device
i get this:
● sys-devices-pci0000:00-0000:00:14.0-usb1-1x2d6.device -
/sys/devices/pci0000:00/0000:00:14.0/usb1/1x2d6
Loaded: loaded
Active: inactive (dead)
--
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
