I would first suggest rebuilding new pulseaudio configuration for your user account. This might, in most cases, fix the problem or at least rule out issues related to pulseaudio configuration.
Old pulseaudio configuration files can sometimes conflict with newer versions of pulseaudio after package or system upgrades. To fix this, please follow the steps below:
Back up ~/.config/pulse/ configuration directory to ~/.config/pulse_old/ by running the following command in the terminal:
mv ~/.config/pulse/ ~/.config/pulse_old/
After that, please reboot your system to build new pulseaudio configuration files. A new ~/.config/pulse/ directory will be created automatically.
Test your audio now.
If, somehow, after applying this fix you decide to go back to the previous state before applying the fix, please follow the steps below:
Run the following command in the terminal:
rm -r ~/.config/pulse/
Run the following command in the terminal:
mv ~/.config/pulse_old/ ~/.config/pulse/
Reboot your system.
However, if all is okay and the problem is fixed, you can remove the backed up old configuration directory ~/.config/pulse_old/ to free space ( if you wish ) by running the following command in the terminal:
I faced the same issue, you can follow steps mentioned in the answer of this question. If the link doesn't work just do this.
Open your terminal and after that:
sudo vim /etc/default/grub
Find GRUB_CMDLINE_LINUX_DEFAULT and add snd_hda_intel.dmic_detect=0 to the end of it. (ex: GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 snd_hda_intel.dmic_detect=0")
It also happened to me a couple of times, though I can't remember if rebooting used to solve my problem... Anyway I found the following line to be helpful:
pulseaudio -k && sudo alsa force-reload
I can't find the original thread with the solution and explanation, but it's practically shutting/killing the deamon and forcing alsa to reload.
I would first suggest rebuilding new pulseaudio configuration for your user account. This might, in most cases, fix the problem or at least rule out issues related to pulseaudio configuration.
Old
pulseaudio
configuration files can sometimes conflict with newer versions ofpulseaudio
after package or system upgrades. To fix this, please follow the steps below:Back up
~/.config/pulse/
configuration directory to~/.config/pulse_old/
by running the following command in the terminal:After that, please reboot your system to build new
pulseaudio
configuration files. A new~/.config/pulse/
directory will be created automatically.Test your audio now.
If, somehow, after applying this fix you decide to go back to the previous state before applying the fix, please follow the steps below:
Run the following command in the terminal:
Run the following command in the terminal:
Reboot your system.
However, if all is okay and the problem is fixed, you can remove the backed up old configuration directory
~/.config/pulse_old/
to free space ( if you wish ) by running the following command in the terminal:I faced the same issue, you can follow steps mentioned in the answer of this question. If the link doesn't work just do this.
Open your terminal and after that:
sudo vim /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT
and addsnd_hda_intel.dmic_detect=0
to the end of it. (ex:GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 snd_hda_intel.dmic_detect=0
")sudo grub-mkconfig -o /boot/grub/grub.cfg
I have found a similar problem in a different thread, you might want to try this:
It also happened to me a couple of times, though I can't remember if rebooting used to solve my problem... Anyway I found the following line to be helpful:
I can't find the original thread with the solution and explanation, but it's practically shutting/killing the deamon and forcing alsa to reload.
My solution is a mixed several threads: this thread and that, another one and latest: