Hello Team
Getting a strange problem in that sound works from within my host OS (Fedora 16 64bit)
I boot up my VM (VirtualBox) and sound works fine in the VM and on the host
After a period of time sound stops working in the VM (could be a couple of hours)
I drop back to my host OS to test the sound from there...and this is where it gets interesting
1. When I change the volume from the desktop I here no alert sound (ping bark, drip...whatever)
2. If I go into sound setting and change the volume I can hear the alerts
3. Other than the changing volume from the speaker icon on the desktop sound work fine from the host OS but nothing in the VM?
This is pretty much a standard out of the box fedora 16 install with Gnome 3 as the desktop.
I am sure that this has nothing to do with it but I am running the host OS from an external hard drive to test before I upgrade from Fedora 14 to 16. Also migrated off of VMware to Virtualbox to host my Windoz work instance.
Thanks for your help team
Stu
In /var/log/messages I can see the below error messages
Code:
Mar 27 15:16:00 bwork pulseaudio[3267]: pid.c: Daemon already running.
Mar 27 15:31:42 bwork pulseaudio[3259]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy
Mar 27 16:20:32 bwork rtkit-daemon[2236]: Successfully made thread 3510 of process 3259 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Mar 27 16:20:37 bwork rtkit-daemon[2236]: Successfully made thread 3511 of process 3259 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Mar 27 16:37:13 bwork bluetoothd[1224]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Mar 27 16:37:13 bwork bluetoothd[1224]: bluetoothd[1224]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Mar 27 16:37:53 bwork rtkit-daemon[2249]: Successfully made thread 2248 of process 2248 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11.
Mar 27 16:37:53 bwork rtkit-daemon[2249]: Successfully made thread 2263 of process 2248 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Mar 27 16:37:53 bwork rtkit-daemon[2249]: Successfully made thread 2264 of process 2248 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Mar 27 16:37:53 bwork rtkit-daemon[2249]: Successfully made thread 2265 of process 2248 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Mar 27 16:38:09 bwork rtkit-daemon[2249]: Successfully made thread 2471 of process 2471 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Mar 27 16:38:10 bwork rtkit-daemon[2249]: Successfully made thread 2477 of process 2471 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Mar 27 16:38:13 bwork rtkit-daemon[2249]: Successfully made thread 2518 of process 2518 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Mar 27 16:38:13 bwork pulseaudio[2518]: pid.c: Daemon already running.
Mar 27 16:40:04 bwork pulseaudio[2471]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy
Mar 27 16:40:04 bwork pulseaudio[2471]: sink-input.c: Failed to create sink input: sink is suspended.
Mar 27 16:40:04 bwork pulseaudio[2471]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy
Mar 27 16:40:37 bwork pulseaudio[2471]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy
Mar 27 16:40:37 bwork pulseaudio[2471]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy
Mar 27 16:40:48 bwork pulseaudio[2471]: alsa-sink.c: Error opening PCM device front:0: Device or resource busy
Linear Mode
