I’m not sure if this is the correct forum, but I started seeing some new error log messages a few days ago. Here are the messages:
Dec 07 16:34:01 Mobile-PC pulseaudio[1794]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dec 07 16:34:01 Mobile-PC pulseaudio[1794]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Dec 07 16:34:01 Mobile-PC pulseaudio[1794]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Here is the extent of how long they have been occurring:
Dec 06 13:45:48 Mobile-PC pulseaudio[1607]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dec 07 11:05:52 Mobile-PC pulseaudio[4629]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dec 07 16:34:01 Mobile-PC pulseaudio[1794]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
I run sudo rpmconf -at after most updates, and on the Dec. 4, the date alsa-ucm-conf was updated, a new /etc/pulse/daemon.conf showed up. I installed the new configuration file and set flat-volumes = no in the new file. I just ran rpmconfigcheck and nothing showed up:
> sudo rpmconfigcheck
Searching for unresolved configuration files
Interesting, I see that flat-volumes is already being set to no in /etc/pulse/daemon.conf.d/60-disable_flat_volumes.conf. I was unaware of the contents of this file:
> cat /etc/pulse/daemon.conf.d/60-disable_flat_volumes.conf
# Set flat-volumes to no so that no applications can abruptedly increase master volume
# Remedy for fate#310668.
flat-volumes = no
It looks like I need to figure out how to report the issue to the ALSA developers.