Actually, I believe this is fixed as of precise, as the apparmor policy
refuses writes from the container into the /sys/devices/*/uevent files.
(udevadm trigger --add writes 'add' into those files).
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug not
This is due to the container running udevadm trigger --action=add.
Those events also get sent to the host, causing some hardware to be
reset. For me, in addition to sound levels being reset, my keyboard
bindings are also reset.
This won't happen with a Precise guest as it won't run udev. At the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948447
Title:
Starting an LXC changes the volume (sound!) of the host
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
