https://bugs.freedesktop.org/show_bug.cgi?id=52483
--- Comment #5 from Tanu Kaskinen <[email protected]> 2012-09-08 10:20:14 UTC --- Thinking this a bit more, using "sudo -H" quite likely won't work either. The default model is that while one user has a session active, nobody else has access to the audio hardware, so having $HOME properly set doesn't help much. Using the system-wide mode is currently probably the easiest way of making this particular use case work, but it has its downsides. I'm not aware of any simple solutions that wouldn't also have severe drawbacks, so a fix for this bug is not likely to happen soon (I barely have enough time for patch review, so I don't do much coding myself nowadays). If someone is willing to work on this, I have some ideas for a not-so-simple solution (basically a hybrid model where there's a system-wide pulseaudio instance talking to the hardware and taking care of access control, and per-user instances that connect to the system-wide instance). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. You are the assignee for the bug. _______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
