For the record, this behavior disappears if I change the rule from:
SUBSYSTEMS=="usb", ATTRS{whatever}=="whatever", SYMLINK+="ttyWhatever"
to:
SUBSYSTEM=="tty", ATTRS{whatever}=="whatever", SYMLINK+="ttyWhatever"The first rule didn't actually match the TTY device at the leaf of the device tree. I suspect it must have been matching the cdc_acm USB device that is one level above the TTY device in the hierarchy. So in all likelihood, the "correct" rule is the second one, And this rule does work the same way regardless of whether the device is disconnected and reconnected, or `udevadm trigger` is run. I do think the current udev behavior is still a bug, though: either the first rule should always fail, or should always work. The fact that the symlink works correctly with the first rule only when udevadm is manually triggered, but not when the device is removed and re-added, cannot be the expected behavior. (Right?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778833 Title: tty symlink incorrect after disconnect/reconnect, fixed by manual udevadm trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1778833/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
