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

[Launchpad Bug Tracker]

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
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/925122

Title:
  container's udevadm trigger --add affects the host

Status in “lxc” package in Ubuntu:
  Invalid
Status in “udev” package in Ubuntu:
  Fix Released

Bug description:
  When the container does 'udevadm trigger --add' (in
  /etc/init/udevtrigger.conf), the host re-processes all those events
  too.  This can lead (less importantly) to keyboard settings and
  soundcard levels being reset, but (more importantly) could presumably
  also cause worse troubles.

  Once upstart has a concept of being ina  container, udev should be
  updated to not run udevtrigger.conf when in a container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925122/+subscriptions