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

[Stéphane Graber]

I applied the change to our packaging branch for udev but didn't upload
yet as the new upstart failed to build on armel, armhf and powerpc.

Uploading the change with the current upstart would most likely break if
not slow down the boot.

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

** Changed in: udev (Ubuntu)
     Assignee: (unassigned) => Stéphane Graber (stgraber)

-- 
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 Committed

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