[Bug 1167588] New: Pulse Audio using virtualbox has no sound
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 Bug ID: 1167588 Summary: Pulse Audio using virtualbox has no sound Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: ace6zip@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36 Build Identifier: Using the latest tumbleweed 2020/03/22 and virtualbox 6.1.4 (tumbleweed host) Pulse Audio version 11 All guest VMs with PulseAudio and Intel HD Audio do not produce sound. Different audio settings do not produce sound. With Leap 15.1 as host and virtualbox 6.0.12 the same VMs do work properly with Pulse Audio Version 11 Reproducible: Always Steps to Reproduce: 1. Run VM (Windows 10 or Leap) guest under virtualbox 2. Using chrome browser play sound from youtube 3. The example of a good and bad vb log shows the following difference VBox.log.1 shows working, VBox.log.2 show failure. VBox.log.1:00:00:05.666638 Driver <string> = "PulseAudio" (cb=11) VBox.log.1:00:00:05.666646 DriverName <string> = "PulseAudio" (cb=11) VBox.log.1:00:00:05.834124 Audio: Initializing PulseAudio driver VBox.log.1:00:00:05.837151 PulseAudio: Using v11.1.0 VBox.log.1:00:00:05.838495 PulseAudio: Retrieving server information ... VBox.log.2:00:00:08.499673 Driver <string> = "PulseAudio" (cb=11) VBox.log.2:00:00:08.499678 DriverName <string> = "PulseAudio" (cb=11) VBox.log.2:00:00:08.619947 Audio: Initializing PulseAudio driver VBox.log.2:00:00:08.622795 PulseAudio: Using v13.0.0 VBox.log.2:00:00:08.623157 PulseAudio: Failed to connect to server: Connection refused VBox.log.2:00:00:08.623263 PulseAudio: Retrieving server information ... VBox.log.2:00:00:08.623275 PulseAudio: Server information not available, skipping enumeration VBox.log.2:00:02:11.479897 PulseAudio: Retrieving server information ... VBox.log.2:00:02:11.479918 PulseAudio: Server information not available, skipping enumeration -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c1 --- Comment #1 from Craig Andersen <ace6zip@gmail.com> --- The sound was fine with host Leap 15.1 using PulseAudio 11 but tumbleweed and Leap 15.2 virtualbox hosts using PulseAudio 13 sound has not worked on any clients for weeks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 Craig Andersen <ace6zip@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- OS|openSUSE Factory |All -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c2 --- Comment #2 from Larry Finger <Larry.Finger@gmail.com> --- On my Tumbleweed host and Leap 15.2 guest, the sound works. The guest uses PulseAudio with an ICH AC97 controller. There has been one report of fixing the sound by switching to an Intel HD Audio controller, and then back to ICH AC97. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c3 --- Comment #3 from Craig Andersen <ace6zip@gmail.com> --- Just ran the tests again with no change. Updates Tumbleweed host with latest patches (8/23/2020). Host is Intel NUC 7i7 running latest tumbleweed updates (kernel 5.7.11). Sound is through an HDMI interface. Updated VB client Leap 15.2 with all patches. Set sound to Pulseaudio + Intel HD Audio results no client sound. Poweroff the client. Change audio settings to Pulseaudio + ICH AC97. No client sound. For me the Client log still indicates 00:00:01.050709 [/Devices/ichac97/0/AudioConfig/] (level 4) 00:00:01.050712 Driver <string> = "AUDIO" (cb=6) 00:00:01.050713 Driver <string> = "PulseAudio" (cb=11) 00:00:01.050717 DriverName <string> = "PulseAudio" (cb=11) 00:00:01.050720 Driver <string> = "AUDIO" (cb=6) 00:00:01.050721 Driver <string> = "AUDIO" (cb=6) 00:00:01.157236 Audio: Initializing PulseAudio driver 00:00:01.158930 PulseAudio: Using v13.0.0 00:00:01.159162 PulseAudio: Failed to connect to server: Connection refused 00:00:01.159243 PulseAudio: Retrieving server information ... 00:00:01.159249 PulseAudio: Server information not available, skipping enumeration I have yet to see Pulseaudio v13 work on VB client. For me the Leap 15.1 host with Pulseaudio v11 does work. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c4 --- Comment #4 from Larry Finger <Larry.Finger@gmail.com> --- The only "fix" for a "Connection refused" error with an audio server that I have found thus far is as follows: In /etc/pulse/client.conf add default-server = 127.0.0.1 and add load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1 into /etc/pulse/default.pa My system has neither of these changes, and still works. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c5 --- Comment #5 from Craig Andersen <ace6zip@gmail.com> --- Indeed that patch is on the net, however when it is applied to the Tumbleweed host, it loses the audio device locally. I am assuming the changes apply to the host not Leap 15.2 client. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c6 --- Comment #6 from Craig Andersen <ace6zip@gmail.com> --- I guess I must live with the no sound on VM client for a while because the audio drivers, mixers, ... oh my !? make it difficult to diagnose. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c7 --- Comment #7 from Larry Finger <Larry.Finger@gmail.com> --- Yes, the configuration changes were for the host. Audio has long been a problem with Linux. It would be a lot easier to diagnose this problem if I could duplicate it. The whole process of debugging is a lot easier if one can attach gdb and step through the offending code. I looked at the code where the server connection is refused, and that is more opaque than most of the VB code - I did not think that was impossible! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c8 --- Comment #8 from Craig Andersen <ace6zip@gmail.com> --- Thanks for your efforts, I will just live with it. It was just that it went from Leap 15.1 host working with pulseaudio v11 to tumbleweed or Leap 15.2 host not working with pulseaudio v13. I may load tumbleweed or Leap 15.2 from scratch. The client does seem to work on Leap 15.1 host. I am not a novice to linux or tumbleweed it is just that there are too many parts here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c9 --- Comment #9 from Craig Andersen <ace6zip@gmail.com> --- Another trial Installed and updated a new Leap 15.2 host. The Leap 15.2 client has the same audio issue with pulseaudio + ACH97. Tried Leap 15.1 host. With the Leap 15.2 client with pulseaudio + ACH97 it aborts. Changed pulseaudio to ALSA and sound for Leap 15.2 client worked. At this point I need to get off the client audio merry-go-round. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c10 --- Comment #10 from Craig Andersen <ace6zip@gmail.com> --- Ok, it's a new year. What I have figured out is that it has to do with how pulseaudio starts. Leap 15.1 [1] UserX logs into system with KDE plasma desktop [2] The pulseaudio starts as /usr/bin/pulseaudio --start --log-target=syslog [3] Virtualbox is started by root audio on clients works with pulseaudio + Intel HD Audio settings In Leap 15.2 and Tumbleweed [1] UserX logs into system with KDE plasma desktop [2] the pulseaudio starts as /usr/bin/pulseaudio --daemonize=no --log-target= journal [3] Virtualbox is started by root audio on clients can not connect to pulseaudio What seems to change is that under 15.1 pulseaudio is a daemon (--start implies daemon) and under 15.2 and Tumbleweed pulseaudio is started by systemd as a --user service. systemctl --user status pulseaudio.service ��� pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; disabled; vendor preset: disabled) Active: active (running) since Sun 2021-02-14 06:57:03 CST; 6h ago TriggeredBy: ��� pulseaudio.socket Main PID: 1621 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service ������1621 /usr/bin/pulseaudio --daemonize=no --log-target=journal ������1676 /usr/libexec/pulse/gsettings-helper Feb 14 06:57:03 hydrax systemd[1406]: Starting Sound Service... Feb 14 06:57:03 hydrax systemd[1406]: Started Sound Service. I now need to figure how a VB client can log into the pulseaudio daemon ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1167588 http://bugzilla.opensuse.org/show_bug.cgi?id=1167588#c11 --- Comment #11 from Craig Andersen <ace6zip@gmail.com> --- After looking at the internet and Larry's info from 2020-08-25 I realized I needed to put the "default-server = 127.0.0.1" in the non desktop users (root) ~/.pulse/client.conf file. And now it works. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com