Comment # 10 on bug 1167588 from Craig Andersen

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 ?