Pulseaudio protocol native c denied access to client with invalid authentication data

Pulseaudio daemon not running for pacmd

I’m currently trying to make HSP bluetooth profile works on a custom board based on Atmel SAMA5D2. I’m using a custom Linux made from Buildroot-2017-08.

I’m at the point where I try to configure pulseaudio. The pulseaudio package is the one from buildroot and I ticked «start as system daemon».

When the system starts, pulseaudio seems to be running

However when I try to communicate with the daemon it fails

I realized that the message change if I export the following environement variable

Concerning rights to access this folder here they are

From this question Problems with pulseaudio — pavucontrol and pacmd not connecting to pulseaudio I tried to change rights about the directory but it didn’t changed anything.

It seems that there are some problems when looking at logs but I can’t say if this is a big deal or not.

Also I have no choice to run pulseaudio as root because there is no other user on my target.

EDIT :

After restarting pulseaudio in verbose mode (-vvv) it seems that the problem comes from an invalid connection data

After adding root user to pulse group the problem persists.

EDIT 2 :

Changing the process access rights to allow pulse group’s members to read/write and execute files seems to unlock a bit the situation as I can now communicate with the daemon but not act on it.

Источник

Pulseaudio protocol native c denied access to client with invalid authentication data

I’m running Debian Stretch on a RPi 3 and to play audio via my bluetotth box without any luck. This is basically what I did:

My bluetooth box is connected, but I don’t get any audio output, because of this error:

What I tried to solve it:

[*]The users (root, pi and mopidy) are in the groups pulse, pulse-access and audio
[*]Added that line to system.pa load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/my-pulse-socket-name and added the file

/.config/pulse/client.conf with that content default-server = unix:/tmp/my-pulse-socket-name

Thanks in Advance — Configs are on GitHub, but I’m not allowed to post more than two links.

If I start pulseaudio with pulseaudio -D I’m able to play soundfiles via bluetooth but only with the current user. (i.e. If I started with user pi, the user tringler cannot use the bluetooth box)
If I start pulseaudio with pulseaudio —start my bluetooth box will not connect at all
If I start the systemd service nobody can play soundfiles and I get the Denied Access errors

Re: Pulseaudio:“Denied access to client with invalid authentication data”

PulseAudio is no longer needed for Bluetooth audio streaming in Raspbian Stretch; it’s functionality is replaced by BluesALSA. I would start by uninstalling PulseAudio.

Источник

Pulseaudio protocol native c denied access to client with invalid authentication data

I know this an Ubuntu forum and not a raspbian forum, but that topic is not directly related to RPi and Raspbian.
I’m running Debian Stretch on a RPi 3 and to play audio via my bluetotth box without any luck. This is basically what I did:

My bluetooth box is connected, but I don’t get any audio output, because of this error:

● pulseaudio.service — Pulse Audio
Loaded: loaded (/etc/systemd/system/pulseaudio.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2017-09-05 00:23:34 CEST; 19min ago
Main PID: 336 (pulseaudio)
CGroup: /system.slice/pulseaudio.service
└─336 /usr/bin/pulseaudio —system —disallow-exit —disable-shm —exit-idle-time=-1

Sep 05 00:41:52 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:42:05 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:42:18 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:42:22 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:42:25 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:42:38 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:42:52 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:43:05 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:43:08 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
Sep 05 00:43:21 raspberrypi pulseaudio[336]: W: [pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.

What I tried to solve it:

The users (root, pi and mopidy) are in the groups pulse, pulse-access and audio

Added that line to system.pa load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/my-pulse-socket-name and added the file

/.config/pulse/client.conf with that content default-server = unix:/tmp/my-pulse-socket-name

Thanks in Advance!

PA Config:
system.pa: https://gist.github.com/tringler/c3935577cf00c333e072ee17c99b0f5f
default.pa: https://gist.github.com/tringler/2fce9b1bfc92c5d114f26c32bd8a5255
daemon.conf: https://gist.github.com/tringler/dff6f4ec9e2fd5614f315f3d44b38a2b
client.conf: https://gist.github.com/tringler/fae77ddaa1ae69a70078663c7f88edaf

PulseAudio Log: https://gist.github.com/tringler/f88b227e99624ad990b836dda9de5507

/.config/pulse/cookie. THis doesn’t work

$ paplay test.wav
Connection failure: Access denied

DISPLAY= paplay test.wav

So something in the X11 auth is messing it up. Unsetting the DISPLAY environment variable was good enough for me.

Источник

What user settings control audio access?

Running a regularly updated 10.04 LTS we have a weird issue with access to audio with pulseaudio 0.9.22. Sound device is ATI Technologies Inc SBx00 Azalia (Intel HDA)

• Login user1 after reboot: sound OK
• Login user2 after reboot: sound OK
• Login user1 then user2: sound OK: both have sound

• Login user2 then user1: only user2 has sound
• Login user2 after boot, logout user2, then login user1: no sound

• Login user3 then user1: all is good!

In the two latter cases user1 is getting repeated errors in syslog:

protocol-native.c: Denied access to client with invalid authorization data

These errors disappear only after pulseaudio is started from user1 manually in a terminal. Then audio access is fine for both. There is an error module-alsa-card.c: Failed to find a working profile but still sound output is fine.

We both are not a member of the Audio Group. Deleting

/.pulse from both accounts has no effect on this behaviour.

The issue started in 9.10 Karmic and continued to be there even after an upgrade to 10.04 Lucid LTS. This indicates that some erroneous settings survived the upgrades.

The dependency on boot order of users indicates that some other user specific settings may be involved, but we have no idea where to start searching. From tests with 3 users it seems that only settings for user2 are broken.

Loading pulseaudio modules module-esound-protocol-unix and module-native-protocol-unix with the option auth-anonymous=1 in both default.pa, and system.pa did not change this behaviour. Neither did it help to delete pulseaudio cookies

/.pulse-cookie from both users.

Added here is our default.pa and our system.pa.

Suggestions 1) to from the answer below did not make a change (running pulseaudio in system mode was not possible) but unplugging the external speaker, rebooting, plugging the speaker back in and reboot again from user1 did the trick.

It is still unclear where this hardware information was (erroneously) stored and why it affected only one user account.

Источник

Thread: pulseaudio appears to be failing after login — 18.04.4

Thread Tools

Display

pulseaudio appears to be failing after login — 18.04.4

Can’t recall anything specific to the timing of when this started. Laptop is an HP dm4 which has been running Ubuntu without issue for some time now. Only dealing with the internal audio to the built-in speakers. Here is what I’m experiencing.

* Boot from power off. At login screen the speaker icon exists in the top right of the screen. I can click on it and if adjusting the level I get the confirmation tone.
* Login, speaker icon no longer present at top right.
Wait for a bit.
* «System problem detected» window appears. No indication what this relates to but I’m willing to bet it is pulseaudio having an issue.
* Open sound settings, no output device listed. Not even the «dummy device» I’ve seen mentioned in some of my research.
* Open a terminal, enter «pulseaudio —check». No exit code returned.
* In terminal, enter «pulseaudio -D». The output device now shows in sound settings and works. (with exception, see below)

So it seems to me that pulseaudio is likely crashing after login. I’m at a loss to explain why. In the troubleshooting that led up to me discovering that «pulseaudio -D» seems to be my temporary fix, I had gone through steps of reinstalling both pulseaudio and alsa-base, forcing reload of alsa, deleting the .config/pulseaudio directory. Hoping for some tips to confirm that the «system problem detected» is pulseaudio crashing, and anything else that could help me progress to solving this.

The «exception» that I mentioned is that even after getting output working the audio test available in the sound settings does not work. I can see the clicks for the left or right channel buttons register, but no audio is heard. Mentioning this separately as I don’t feel it is necessarily tied to the problem of pulseaudio needing to be restarted.

Источник