I'm hesitant to backport, because the change causes significant issues on upgrade, e.g.: https://github.com/systemd/systemd/issues/17605
if we do backport the 'sticky' udev tags, we'll need to make sure to also pull back the proper commits to handle the new udev format across daemon-reexec, e.g.: https://github.com/systemd/systemd/pull/17622 ** Bug watch added: github.com/systemd/systemd/issues #17605 https://github.com/systemd/systemd/issues/17605 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" Status in systemd package in Ubuntu: Confirmed Bug description: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). An example causing by this issue, I had a usb printer (non-ippusbxd) which connected to my laptop, but after unplugging it from my laptop, the .device unit were still present, if a different printer gets plugged to the same USB port then, it won't be configured correctly. [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
