I suggest patching Trusty to remove the lock file on boot, before ebtables has any chance to run, if that's possible. That seems to me to be the minimal fix that would resolve any user impact on Trusty. Using /run is a better way to do that, and in the future we'll do it that way (since Zesty has this fixed) but for a stable release update we prefer the minimal and least disruptive fix over a "correct" one.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file should be moved from /var/lib/ebtables to /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
