Created attachment 902404 [details]
journalctl -ax |egrep -i "snd|pulse|audio|alsa"
Description of problem:
PUlseAudio seems to crash always. There's no sound at all.
$ LC_ALL=C alsamixer
Failed to create secure directory (/run/user/1000/pulse): Permission denied
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused
cannot open mixer: Connection refused
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Upstream seems to be aware: https://bugs.freedesktop.org/show_bug.cgi?id=42804
Created attachment 902405 [details]
dmesg |egrep -i "snd|pulse|audio|alsa"
I have reinstalled alsa-plugins-pulseaudio, restarted, sound works again.
$ su -c 'yum remove -y alsa-plugins-pulseaudio && yum install -y alsa-plugins-pulseaudio'
Well, that could be a workaround / temporary fix:
# chgrp -R pulse /run/user/*/pulse
# usermod -a -G pulse $USER
seems to be an incorrect reference, it talks about
"raop module does not work with shairport"
which doesnt seem relevant here.
before the workaround in comment #3, what was the ownership/permissions of /run/user/1000/pulse
and does 'loginctl' list your session (and as active)?
If its owned by root, I suspect bug #753882 is relevant
(In reply to Rex Dieter from comment #4)
> before the workaround in comment #3, what was the ownership/permissions of
# ls -ld /run/user/1000/pulse/
drwx------. 2 raphael raphael 80 30. Okt 10:49 /run/user/1000/pulse/
# id raphael
uid=1000(raphael) gid=1000(raphael) Gruppen=1000(raphael),991(pulse),1001(build),980(yumex)
I guess additionally to comment #3 the following will be needed:
# chmod g+rx /run/user/*/pulse
(In reply to Rex Dieter from comment #5)
> and does 'loginctl' list your session (and as active)?
SESSION UID USER SEAT
1 1000 raphael seat0
1 sessions listed.
(In reply to Rex Dieter from comment #6)
> If its owned by root, I suspect bug #753882 is relevant
What should be owned by root? I guess it's fatal in general to let root own something under /home … So not sure if bug #753883 is connected anyhow.
# ls -l /run/user
drwx------. 3 root root 60 30. Okt 11:01 0
drwx------. 14 raphael raphael 300 30. Okt 14:25 1000
Summary: I would prefer the solution with setting correct group access.
group access shouldn't be required, why do you think you need it?
*** This bug has been marked as a duplicate of bug 753882 ***