On Tue, 2012-04-24 at 11:24 -0400, Adam Tauno Williams wrote: > On Mon, 2012-04-23 at 18:07 +0200, Paul Menzel wrote: > > Am Mittwoch, den 18.04.2012, 15:24 +0200 schrieb David Henningsson: > > > On 04/18/2012 03:06 PM, Adam Tauno Williams wrote: > > > > D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC0 is accessible: > > > > yes > > > > D: [pulseaudio] module-udev-detect.c: > > > > /devices/pci0000:00/0000:00:1b.0/sound/card0 is busy: yes > > > This means that another process is hogging the sound card, so pulseaudio > > > can not access it. You can use the 'sudo fuser -v /dev/snd/*' command to > > > figure out what process that could be. > > Good catch. I missed that. Adam, did you find a solution? > If I create a new user and login, and start pulseaudio -vvvvv, then > PulseAudio seems to be operational. > The user of the workstation isn't in today, but I'll check what is > locking the sound device when he comes back. Although still puzzled > why Pulse doesn't start initially. So we rebooted, had the user login, run "pulseaudio -vvvvvvvvvv" and .... now they get working PA! So the question is just - why doesn't it start in the first place. Should it get fired up via d-bus when the user logs in, or should be be registered somewhere for session startup? [this is a GNOME 3 box] -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20120425/cfbe8443/attachment.pgp>
