![alsa lib pulse.c:243:(pulse_connect) pulseaudio: unable to connect: access denied alsa lib pulse.c:243:(pulse_connect) pulseaudio: unable to connect: access denied](https://user-images.githubusercontent.com/56457847/132254053-cb5bd8f2-c492-4565-b56e-12a0c84cef55.png)
As root, open the file /etc/nf with your editor.Ģ. I consider this a work-around until a better solution has come up.ġ. Now it no longer floods the system's message log. I have been able to disable this message in /etc/nf. Maybe you should consider tuning down this log message and display it only if debugging is enabled ? The situation with the log files is quite serious, it can fillup a disk in very little time, and also makes it impossible to read the messages files for other log messages as there are millions of identical messages for PA. I needed to change this manually to be able to use my 5.1 speakers on a Sound Blaster Audigi2 card, because PA itself didn't recognize the card had 5.1 output.Ġ5:04.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)įlags: bus master, medium devsel, latency 64, IRQ 16 This may have started happening since I change /etc/pulse/nf to set:
![alsa lib pulse.c:243:(pulse_connect) pulseaudio: unable to connect: access denied alsa lib pulse.c:243:(pulse_connect) pulseaudio: unable to connect: access denied](https://www.k0pir.us/wp-content/uploads/2016/11/PA318830-e1530409353893.jpg)
The message is repeated 10s of times per second (and that by itself seem a bit excessive). I have the same output in my /var/log/messages file, I don't get sound pauses but my messages file becomes Gigabyes big (I deleted it twice already because in a few days as it reached 2GB size each time). Version-Release number of selected component (if applicable): When this happens, audio pauses or repeats the same clip for about 2-3 seconds before recovering. Please report this issue to the PulseAudio developers.
#ALSA LIB PULSE.C:243:(PULSE_CONNECT) PULSEAUDIO: UNABLE TO CONNECT: ACCESS DENIED DRIVER#
Nov 17 11:10:48 tlondon pulseaudio: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Running kernel-2.6.27.86_64 and pulseaudio-0.9.86_64, I get this when I disable wireless by right clicking the NetworkManager icon and un-selecting "Enable Wireless" while rhythmbox is playing.