I also have this bug, though on a multi-user system. I have one user who likes to play "DJ" and leave her music running while another is working at the console. Unfortunately, since PulseAudio pauses as soon as they switch accounts they have decided to work around the problem by not switching accounts! As you can imagine this is a much more serious security problem than the one PulseAudio is trying to address by shutting itself off on VT switch.
It appears, from Googling, that the preferred method of dealing with this bug is to disable the "security" features in PulseAudio. Unfortunately, that also disables many other features (again, in the name of "security") as documented here: http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ In my opinion, PulseAudio's definition of "security" needs to be more flexible. There should be some way to specify that some users do have rights to audio devices even if they do not own the current virtual terminal. I liked the way that ALSA did it, using group "audio" for users with those privileges. PulseAudio really should have an option to allow this model of security. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841909 Title: Pulseaudio does not play in virtual console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/841909/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
