[Bug 925122] Re: container's udevadm trigger --add affects the host

Launchpad Bug Tracker 925122 at bugs.launchpad.net
Fri Feb 17 20:45:12 UTC 2012

This bug was fixed in the package udev - 175-0ubuntu5

udev (175-0ubuntu5) precise; urgency=low

  [ David Henningsson ]
  * Remove jack-detection.patch: Now that PulseAudio uses the new jack
    detection interface, we can remove this patch.

  [ Stéphane Graber ]
  * debian/udev.udevtrigger.upstart: Update to wait for 'container' or
    'not-container' to be emitted, then skip just exit 0 but still run
    post-stop if it's a container and run 'udevadm trigger' if it's not.
    This is needed until we have a proper device namespace preventing
    udev events from affecting the outside.
    (LP: #925122)
  * Make udev depend on upstart >= 1.4-0ubuntu6 to ensure the next reboot
    will indeed either emit container or not-container.
 -- Stephane Graber <stgraber at ubuntu.com>   Fri, 17 Feb 2012 15:40:47 -0500

** Changed in: udev (Ubuntu)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.

  container's udevadm trigger --add affects the host

To manage notifications about this bug go to:

More information about the Ubuntu-server-bugs mailing list