Attaching a pulseaudio log wherein foobar2000 1.3.9/wine-staging somehow
breaks pulseaudio 8, even though foobar2000 never has problems playing
through it, even after restarting foobar2000.
** Attachment added: "pulseverbose.log"
I think I have narrowed this down: pulseaudio 8 goes into its degraded
connection-dropping state after playing some audio in foobar2000 in
wine-staging 1.9.8. I will try to make this fully reproducible.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Forgot to add that you could try cleaning out your pulseaudio
configuration in ~/.config/pulse. You could also check your syslog or
other logs to see if there is any problem with the kernel or systemd
setting up the /dev/shm mount point.
--
You received this bug notification because you are a
Well it may be something local to your system. I just installed and ran
pavucontrol with no such errors, although my install is a fresh 16.04
install from back in December.
Are there any files in /dev/shm related to pulseaudio and your user?
They should be owned by your user, even though your
After it goes into a bad state, connections from Chrome also die
immediately:
(2264.888| 0.801) I: [pulseaudio] client.c: Created 208 "Native client (UNIX
socket client)"
(2264.888| 0.000) I: [pulseaudio] client.c: Freed 208 "Native client (UNIX
socket client)"
(2264.888| 0.000) I:
I have no idea what's going on now: pulseaudio doesn't actually hang and
keeps playing audio, but pavucontrol fails to connect.
# pavucontrol
shm_open() failed: No such file or directory
shm_open() failed: No such file or directory
shm_open() failed: No such file or directory
shm_open()
Thanks, I am now logging and will hopefully see a hang.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1572493
Title:
pulseaudio 8.0 server frequently hangs
Status in pulseaudio
7 matches
Mail list logo
