** No longer affects: pulseaudio (Ubuntu)
** Changed in: linux-oem-5.6 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918880
Title:
pulseaudio
I haven't encountered the problem in over a week after switching to a
5.10 kernel (from linux-image-oem-20.04-edge).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918880
Title:
pulseaudio
No there's no need to change the config file.
I'm guessing now that the issue is the daemon stuck in a system call.
That usually means it's a kernel bug, or a bug in the kernel sound
driver. So if you are comfortable doing so, please try some different
kernel versions:
"; realtime-scheduling = yes" is commented away in
/etc/pulse/daemon.conf (this is a very fresh install of 20.04 and I
haven't customized much). Should I enable this?
Either way, I'll try to exercise suspend and keep an eye out for this
issue happening again. I tried looking around but didn't
Please check that you haven't enabled:
realtime-scheduling = yes
in /etc/pulse/daemon.conf. And if the problem continues to occur after
that then please report it to the developers at:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues
and tell us the new issue ID.
** Changed
