Hide Forgot
Description of problem: On RHEV-M ic155, I have 5.8 hosts and a RHEL 6.3 guest on the host. I try to run alsamixer as "su" and get the following error. If I change user to the user that logged into RHEL 6.3, I can use alsamixer with no error. This does not happen on a RHEL 5.8 guest. [root@dhcp66 ~]# alsamixer ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect: Connection refused cannot open mixer: Connection refused [root@dhcp66 ~]# su test [test@dhcp66 root]$ alsamixer [test@dhcp66 root]$ exit exit [root@dhcp66 ~]# exit Version-Release number of selected component (if applicable): RHEL 6.3 How reproducible: 100% Steps to Reproduce: 1. Install RHEL 6.3 as a guest on a 5.8 host within RHEV-M ic155. 2. Change to su and type alsamixer. 3. Actual results: The alsamixer utility connection was refused. Expected results: The alsamixer utility should appear. Additional info:
this is not a spice bug, please reassign
Does 'alsamixer -c 0' work? You may also remove the pulseaudio packages from the virtual machine. It should have same effect.
I just installed RHEV-M sm111 (2.2) and added two 5.8 hosts and if you are 'su' alsamixer still fails. I just confirmed that 'alsamixer -c 0' does work in RHEV-M sm111.
I think that it belongs to the pulseaudio configuration in RHEL 6.3..
Is this running without a GUI? If so, users must manually copy the pulseaudio cookie file around to be able to connect to pulseaudio. as root, do: mkdir /root/.pulse cp /home/user/test/.pulse/cookie /root/.pulse/cookie then try: alsamixer again.
I have looked and cant find this in the documentation, anywhere. Is this documented?
It is not sufficiently documented, IMO. It depends a bit on the modules you load, but the default one uses a cookie to authorize clients. There is a hint about the cookie in the manpage but I'll see if it can be more more explicit.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0655.html