eyrieowl, I don't use VMWare and still experience the bug. It happens when one user actually uses audio, then the other is not permitted to do so. It doesn't matter if it is a VMWare, which locks the audio output, or rhythmbox, or whatever else. If there is a process talking to the audio output, then upon user switch, the other user is prevented from accessing the output. So this is the pulseaudio issue - or actually pulseaudio/udev/policykit one.
eyrieowl, I don't use VMWare and still experience the bug. It happens when one user actually uses audio, then the other is not permitted to do so. It doesn't matter if it is a VMWare, which locks the audio output, or rhythmbox, or whatever else. If there is a process talking to the audio output, then upon user switch, the other user is prevented from accessing the output. So this is the pulseaudio issue - or actually pulseaudio/ udev/policykit one.