Description of problem: Nothing plays sound. alsamixer says "connection refused". Version-Release number of selected component (if applicable): 6.0 How reproducible: Always Steps to Reproduce: 1. Try to play something Actual results: No sound. Expected results: Sound. Additional info: Downgrade to PA 5.0 works. Maybe related to Bug 1206731 (which is about F22, not F21)
Try restarting your session after installing the update? Can you attach the output from: pulseaudio -vvv Can you attach the output from: alsa-info.sh (it may download a newer version of itself, for you to run)
Of course I rebooted after the update. Turns out PulseAudio 6.0 no longer starts by itself. When I run it manually, it runs just fine. *downgrades to 5.0 again*
1. What happens if you run by hand: $ start-pulseaudio-x11 (that's essentially what is supposed to autostart with your session) 2. What kind of DE/session are you using? gnome, kde, other?
I use Plasma 4. As for the first question: Is that all you need or will you need additional output? I don't want to upgrade and downgrade all the time.
I see this too, pulseaudio is not starting $ journalctl -b | grep -i pulse Mar 29 18:00:22 localhost gnome-session[1155]: WARNING: App 'pulseaudio.desktop' exited with code 1 Mar 29 18:00:23 localhost gnome-session[1155]: gnome-session[1155]: WARNING: App 'pulseaudio.desktop' exited with code 1 $ pulseaudio -D starts it and restores sound until next boot
instead of 'pulseaudio -D', what happens when you try: start-pulseaudio-x11 ? (that's what runs via /etc/xdg/autostart/pulseaudio.desktop)
running start-pulseaudio-x11 fails $ start-pulseaudio-x11 Connection failure: Connection refused pa_context_connect() failed: Connection refused $ sudo start-pulseaudio-x11 Connection failure: Connection refused pa_context_connect() failed: Connection refused
Please attach/post the contents of /etc/pulse/daemon.conf /etc/pulse/client.conf
Created attachment 1010937 [details] contents of /etc/pulse/daemon.conf
Created attachment 1010938 [details] contents of /etc/pulse/client.conf
It's not clear to me why pulseaudio autospawn is failing for you, which those /usr/bin/pactl load-module ... calls are supposed to do. Ah, I forgot one more possibility, check ~/.pulse/client.conf (in addition to /etc/pulse/client.conf) and see if it contains autospawn=no If it does, remove that line, or change to autospawn=yes
changing autospawn = no to autospawn = yes in ~/.pulse/client.conf seems to fix it for me. Thank-you Rex.
OK, I guess we can consider that a regression in autostart behavior, I'll re-add /usr/bin/pulseaudio --start "$@" to /usr/bin/start-pulseaudio-x11 script
pulseaudio-6.0-2.fc21.1 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/pulseaudio-6.0-2.fc21.1
Package pulseaudio-6.0-2.fc21.1: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pulseaudio-6.0-2.fc21.1' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5586/pulseaudio-6.0-2.fc21.1 then log in and leave karma (feedback).
I realised I had autospawn = no in ~/.pulse/client.conf for my jack setup, which I use only occasionally. It kills pulse on startup and starts it again with a custom config file. Before update (with autospawn = yes) this was broken. After update to pulseaudio-6.0-2.fc21.1 I changed back to autospawn = no and rebooted. All seems to be working as it should.
pulseaudio-6.0-2.fc21.1 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1209200 has been marked as a duplicate of this bug. ***
This happens with Fedora 22 again. [syl@virt ~]$ rpm -qa pulseaudio pulseaudio-module-x11 pulseaudio-6.0-2.fc22.x86_64 pulseaudio-module-x11-6.0-2.fc22.x86_64 [syl@virt ~]$ LC_ALL=C bash -x start-pulseaudio-x11 ... + /usr/bin/pactl load-module module-x11-publish display=:0 Connection failure: Connection refused pa_context_connect() failed: Connection refused
Re: comment #19 did you disable autospawn?
Yes, I disabled the autospawn into ~/.pulse/client.conf.
Why? Is it some usecase could not be handled by pasuspender ?
I didn't know about pasuspender. it doesn't work with aliases, it only accepts programs.
As Sylvain Petreolle, i noticed that in root environment,( tested in MATE desktop environment ), that pulseaudio does not start at the beginning of the graphic session. Once logged I also get like Sylvain: # LC_ALL=C bash -x start-pulseaudio-x11 + set -e + '[' x:0.0 '!=' x ']' + /usr/bin/pactl load-module module-x11-publish display=:0.0 Connection failure: Connection refused pa_context_connect() failed: Connection refused == I get this result with autospan enble or not in : /etc/pulse/client.conf (I have no ~/.pulse/client.conf in root home directory! === I tried this with last fedora 22 update, and even with the last fedora-updates-testing enabled to install: pulseaudio-6.0-4 (instead of 6.0-2) # rpm -qa | grep pulseaudio | sort alsa-plugins-pulseaudio-1.0.29-1.fc22.x86_64 pulseaudio-6.0-4.fc22.x86_64 pulseaudio-libs-6.0-4.fc22.i686 pulseaudio-libs-6.0-4.fc22.x86_64 pulseaudio-libs-glib2-6.0-4.fc22.x86_64 pulseaudio-module-bluetooth-6.0-4.fc22.x86_64 pulseaudio-module-gconf-6.0-4.fc22.x86_64 pulseaudio-module-x11-6.0-4.fc22.x86_64 pulseaudio-utils-6.0-4.fc22.x86_64 wine-pulseaudio-1.7.44-1.fc22.i686 wine-pulseaudio-1.7.44-1.fc22.x86_64 ==== So currently the only bug turn around is the suggestion of Rex Dieter in comment 7 of the following bugzilla entry: https://bugzilla.redhat.com/show_bug.cgi?id=1209200 ==> insert /usr/bin/pulseaudio --start in the file: /usr/bin/start-pulseaudio-x11
I confirm that pulseaudio does NOT run under the root environment. FC 22 pulseaudio 6.0-4.fc22