My patch was not for global manipulation of asoundrcs. The global part
was just more of a wishlist on my part. The patch I have submitted only
lets you specify the target user when applying any changes via
asoundconf, so that a user can use asoundconf in usecases like a udev
scripts. Is this still
Global changes belong in /etc/asound.conf. Manipulating asoundrcs
globally, however, cannot handle use cases like ALSA's OSS emulation,
which will break without additional environment variables being passed
to the application. In such cases, an asoundrc is insufficient.
The correct mechanism is
** Changed in: alsa-utils (Ubuntu)
Status: In Progress => Confirmed
--
asoundconf restricted to current user
https://bugs.launchpad.net/bugs/280425
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Attachment added: "add functionality to specify user"
http://launchpadlibrarian.net/18347262/asoundconf_patch
** Changed in: alsa-utils (Ubuntu)
Status: New => In Progress
--
asoundconf restricted to current user
https://bugs.launchpad.net/bugs/280425
You received this bug notifica
