4A Audio crashes pulseaudio with "PCM Fail to Get Authorisation" error

Description

Boot board with specified environment and pulseaudio crashes:

Nov 30 03:49:16 dra7xx-evm systemd[550]: Starting Sound Service... Nov 30 03:49:16 dra7xx-evm pulseaudio[619]: W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). Nov 30 03:49:17 dra7xx-evm pulseaudio[619]: LaunchCallRequest: Fail ws-client=unix:/run/user/0/apis/ws/ahl-4a query=stream_open&{ "audio_role": "Fallback", " Nov 30 03:49:17 dra7xx-evm pulseaudio[619]: PCM Fail to Get Authorisation Nov 30 03:49:17 dra7xx-evm pulseaudio[619]: AlsaPcmHook Plugin Policy Control Fail PCM=Fallback Nov 30 03:49:17 dra7xx-evm pulseaudio[619]: E: [pulseaudio] module.c: Failed to load module "module-alsa-sink" (argument: "device=Fallback"): initialization Nov 30 03:49:17 dra7xx-evm pulseaudio[619]: E: [pulseaudio] main.c: Module load failed. Nov 30 03:49:17 dra7xx-evm pulseaudio[619]: E: [pulseaudio] main.c: Failed to initialize daemon. Nov 30 03:49:17 dra7xx-evm systemd[550]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Nov 30 03:49:17 dra7xx-evm systemd[550]: Failed to start Sound Service.

Environment

dra7xx-evm, USB audio attached, master build with 4A audio enabled, usb-audio HAL selected in 4A configuration file.

blocks

Activity

Show:

Dominig ar Foll 
January 16, 2018 at 3:11 PM

I had that same error during CES preparation.

IN my case it was linked to the faulty default /etc/asound.conf

After "hw:0"  was replaced by a correct entry, the issue went away.

Walt Miner 
January 16, 2018 at 2:34 PM

to do a build for vayu and confirm. 

Walt Miner 
December 19, 2017 at 3:19 AM

Please confirm you agree with resolving this issue.   No fix in gerrit is directly linked to this. 

ronan Le Martret 
December 18, 2017 at 10:45 AM

Curently, pulseaudio is up. I think this issue is close.

Fixed

Details

Assignee

Reporter

Labels

Contract ID

Priority

Created December 1, 2017 at 6:34 PM
Updated February 13, 2018 at 2:44 PM
Resolved December 18, 2017 at 10:45 AM

Flag notifications