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: | pulseaudio | Assignee: | Wim Taymans <wtaymans> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3 | CC: | 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
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 |