36

I sometimes have the problem that I can't hear any sound on my Dell XPS13 with Ubuntu 16.04. I have a Logitech G930 connected to it. When I open pavucontrol it is stuck at "Establishing connection to PulseAudio. Please wait..." I have been following the Ubuntu Audio Problems Guide (german version is here: https://wiki.ubuntuusers.de/Sound_Problembehebung/#Soundsystem ) and found the following:

$ cat /proc/asound/cards
0 [PCH            ]: HDA-Intel - HDA Intel PCH
                     HDA Intel PCH at 0xdc428000 irq 295
1 [H              ]: USB-Audio - Logitech G933 Gaming Wireless H
                     Logitech Logitech G933 Gaming Wireless H at usb->0000:00:14.0-1, full speed

So the sound cards are recognized. However, audio is not played:

$ aplay /usr/share/sounds/alsa/Front_Center.wav 
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Access denied
aplay: main:722: audio open error: Connection refused

Same with sudo:

$ sudo aplay /usr/share/sounds/alsa/Front_Center.wav
Home directory not accessible: Permission denied
Home directory not accessible: Permission denied
Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit >Little Endian, Rate 48000 Hz, Mono

The "groups" command does NOT show the audio group, but what I think is strange that it works most of the time (and often so after restarting, if there are problems) so I'd guess it's not the problem.

Where else could I look?

Edit:

$ lspci -nnk | grep -A2 Audio
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d71]     (rev 
21)
Subsystem: Dell Device [1028:075b]
Kernel driver in use: snd_hda_intel



$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: H [Logitech G933 Gaming Wireless H], device 0: USB Audio     [USB >Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


$ pactl list short sinks
Connection failure: Access denied
Bernie
  • 461
  • We should not be in the audio group, and we should not run audio apps as root. Sometimes deleting poor settings in our HOME need to be deleted. See http://askubuntu.com/questions/201780/how-do-i-debug-issues-with-pulse-audio – Takkat Feb 02 '17 at 13:47
  • Could you please [edit] your question to include the output of the terminal commands lspci -nnk | grep -A2 Audio, aplay -l, and pactl list short sinks? If PulseAudio (via pactl) doesn't respond, please (back up and) remove ~/.pulse, start PulseAudio (pulseaudio --start) and try again. Thanks. – David Foerster Feb 02 '17 at 14:00
  • Sorry, took me a while to reproduce the error and have the time to write everything down. I have edited the question. I have not found a file at ~/.pulse – Bernie Feb 07 '17 at 11:10
  • Hey @Bernie, did you ever got to fix this? Facing the exact same issue.. – Asitis Jul 04 '18 at 14:27
  • Maybe the files are in ~/.config/pulse instead of ~/.pulse. At least on OpenSuSE they are... – rwst Dec 12 '18 at 07:52

7 Answers7

27

This solve the same problem with my:

pulseaudio --check
pulseaudio -D

Taken from: [Solved] Establishing connection to PulseAudio. Please wait ... https://classicforum.manjaro.org/index.php?topic=27044.0

17

I've had this issue since upgrading to 18.04 and read almost all there is about to read about it. I fiddled with the settings, the packages, and eventually it would work sometimes, after installing PulseEffects for getting the right channel throughput for the audio. But then when I would change the audio-output channel to say headphones instead of speakers, the gnome shell crashed. This crash gave me insight to some "obsolete packages" that were still installed and needed removing or upgrading.

So in summary, running these commands solved all my audio problems after a few weeks of debugging (so stupid if you see it now, but whatever works right?)

sudo apt-get update
sudo apt-get upgrade
sudo apt-get remove --purge alsa-base pulseaudio
sudo apt-get install alsa-base pulseaudio pavucontrol
sudo alsa force-reload
reboot

Then

sudo add-apt-repository ppa:mikhailnov/pulseeffects
sudo apt-get update
sudo apt-get install pulseeffects

After a final resetting of the audio output channel, it worked like a charm again.

efthialex
  • 3,831
Asitis
  • 539
  • 3
    I followed everything mentioned above except the last command which gave me an error saying -- unable to locate package pulseeffects..

    Then i did 'pulseaudio --start' and audio started working again.

    – Aseem Dec 13 '18 at 12:06
  • Also got that error and the penultimate command essentially said "nothing to be done" i.e. pavucontrol is already the newest version (3.0-4) and it removed alsamixer – WhereIsTheManual Dec 28 '18 at 18:48
  • Thank you! This worked for 18.10 as well. – Don Jan 23 '19 at 04:00
  • Thank you so much for this answer, I have been trying to solve this issue for a month on 18.10 (new install, not upgrade) after my sound randomly crashed when I was trying to record on audacity. The pulseeffects step wasn't necessary, but like Aseem I needed to do 'pulseaudio --start' – rjb-dev Apr 28 '19 at 06:31
  • sudo apt-get install pulseeffects return error "Unable to locate package pulseeffects" to fix that you need to instll by sudo add-apt-repository ppa:mikhailnov/pulseeffects and then sudo apt update and finally sudo apt install pulseaudio pulseeffects --install-recommends – Naresh Thakur Feb 12 '20 at 02:37
  • Beware, in my system, removing alsa-base and pulseaudio also suggested removing ubuntu-desktop and ubuntu-desktop-minimal, which is an absolute mess. As the other answer suggested, deleting ~/.config/pulse did the trick for me – Guillermo J. May 03 '21 at 14:59
  • DO NOT do this for Linux Mint (cinnamon) removing pulseaudio will also for some bizarre reason also remove Cinnamon [Interblinged dependencies is my guess]. – RyanNerd Aug 04 '21 at 09:31
10

I solved this issue by deleting ~/.config/pulse followed by a reboot.

Eliah Kagan
  • 117,780
Whome
  • 200
  • 4
    +1 I did something similar, which may help with debugging as it doesn't require a reboot: mv ~/.config/pulse ~/.config/pulse.old followed by pulseaudio --start – FriendFX Feb 12 '20 at 02:34
  • 1
    Running Arch Linux and this resolved my issue on i3 – Ari Aug 30 '20 at 05:44
  • 3
    great! removing it and issueing pulseaudio --start did the trick. (Linux Mint 20) – umbe1987 Dec 16 '20 at 16:07
  • 1
    Damn!!! I should had started my research with this one, instead of spending a eon trying complex solutions out – Almir Campos Jul 17 '21 at 05:34
1

systemctl --user restart pulseaudio.service

I found this one on internet and this also work for me. ha ha ha.

1

I have tried every possible solution from everywhere to get the sound working through HDMI on NUC11PAHi7 on Ubuntu 22.04.1 LTS after it stopped working, including the solutions in this thread and none worked. What ended up working is doing the screen lock with windows key L, waiting a minute and then unlocking it. I could not believe it. Hours in terminal trying everything and just locking and unlocking the screen fixed it. I found that answer in a different thread about trying to find realtek drivers for NUC on ubuntu, and now I can't find that thread again to thank them.

rcc
  • 11
0

For me, this issue was being caused by the fact that the UID folder for my user wasnt generated in /run/user/, you can check the UID of your user with id -u. I solved it by logging into my user through a TTY, I'm sure theres a better way to solve this though.

This issue was also preventing me from starting up blueman-applet & blueman-manager

0
pulseaudio -k
pulseaudio -v
sudo reboot 

it worked in my case