[Bug 1906653] Re: Backport systemd to make uevents "sticky"
@Dan I see, thank you anyway :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906653] Re: Backport systemd to make uevents "sticky"
As I mentioned in my last comment, I'm skeptical that the benefit of backporting would outweigh the potential problems it would introduce to existing stable releases. I'm marking this as wont-fix for that reason. I don't think we should consider this unless you can provide specific examples of significant, serious problems that would be fixed by backporting the change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906653] Re: Backport systemd to make uevents "sticky"
for reference, the PR linked in the description is included upstream in v247 so this is fixed in h, i'll mark the bug as such ** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Hirsute) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Focal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906653] Re: Backport systemd to make uevents "sticky"
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906653] Re: Backport systemd to make uevents "sticky"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906653] Re: Backport systemd to make uevents "sticky"
** Description changed: 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906653 Title: Backport systemd to make uevents "sticky" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
