Red Hat Bugzilla – Bug 1269104
pulseaudio not started when logging in as root
Last modified: 2015-11-19 04:29:18 EST
Description of problem: Testing RHEL 7.2 snapshot3 actually Version-Release number of selected component (if applicable): pulseaudio-module-x11-6.0-6.el7.x86_64 pulseaudio-utils-6.0-6.el7.x86_64 pulseaudio-6.0-6.el7.x86_64 pulseaudio-gdm-hooks-6.0-6.el7.x86_64 pulseaudio-module-bluetooth-6.0-6.el7.x86_64 alsa-plugins-pulseaudio-1.0.27-3.el7.x86_64 pulseaudio-libs-6.0-6.el7.x86_64 pulseaudio-libs-glib2-6.0-6.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Install RHEL 7.2 snapshot3 2. Login as root 3. check sound settings Actual results: Sound config panel doesn't show any sound devices because pulseaudio is not running. If you try to play sound with "aplay <file>" then you get a message, that it can't connect to pulseaudio: ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused aplay: main:722: audio open error: Connection refused Expected results: Pulsaudio starts also for the root user. Additional info: This behaviour is now similar to Fedora 22 and there are bugs for Fedora 22 already filed, but not resolved: https://bugzilla.redhat.com/show_bug.cgi?id=1234710 https://bugzilla.redhat.com/show_bug.cgi?id=1226141 Sound works perfectly when logging in as a "normal" user. When you're still in the gdm login screen then pulseaudio is running as a process of gdm. Tried to login from a console and using aplay, but that doesn't work either. So now RHEL 7.2 behaves exactly like Fedora 22. ;-) My fear is that this could affect the sound tests of redhat-hardware-certification.
Autostart is disabled for root so pulseaudio doesn't automatically start on login. A rather easy fix is available for this.
*** Bug 1272241 has been marked as a duplicate of this bug. ***
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-2106.html