Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 812444

Summary: Alsamixer cannot be run as "su" with a RHEL 6.3 guest on a 5.8 host
Product: Red Hat Enterprise Linux 6 Reporter: Bill Sanford <bsanford>
Component: pulseaudioAssignee: Wim Taymans <wtaymans>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3CC: bsanford, cfergeau, jkysela, mkrcmari, pvine, tpelka, wtaymans
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-09 08:24:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bill Sanford 2012-04-13 18:22:06 UTC
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:

Comment 1 Marc-Andre Lureau 2012-04-13 18:33:15 UTC
this is not a spice bug,

please reassign

Comment 2 Jaroslav Kysela 2012-04-23 13:22:34 UTC
Does 'alsamixer -c 0' work?

You may also remove the pulseaudio packages from the virtual machine. It should have same effect.

Comment 3 Bill Sanford 2012-05-04 14:35:16 UTC
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.

Comment 4 Jaroslav Kysela 2014-01-29 09:13:20 UTC
I think that it belongs to the pulseaudio configuration in RHEL 6.3..

Comment 6 Wim Taymans 2014-06-23 15:03:53 UTC
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.

Comment 7 Bill Sanford 2014-09-08 13:10:53 UTC
I have looked and cant find this in the documentation, anywhere. Is this documented?

Comment 8 Wim Taymans 2014-09-08 14:31:25 UTC
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.

Comment 12 errata-xmlrpc 2015-03-09 08:24:59 UTC
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