On Mon, 2017-08-21 at 12:41 +0530, namittal at codeaurora.org wrote:
> Hello,
>
> I am getting this error â??Daemon not respondingâ??.
>
> / # pulseaudio --kill
> / # pulseaudio --start
> W:
> [pulseaudio][/local/mnt/workspace/LE01Aug/poky/build/tmp-glibc/work/armv7a-vfp-neon-oemllib32-linux-gnueabi/lib32-pulseaudio/6.This
> program is not intended to be run as root (unless --system is
> specified).
> D:
> [pulseaudio][/local/mnt/workspace/LE01Aug/poky/build/tmp-glibc/work/armv7a-vfp-neon-oemllib32-linux-gnueabi/lib32-pulseaudio/6.scandir("/home/root/.config/pulse/client.conf.d")
> failed: No such file or directory
> D:
> [pulseaudio][/local/mnt/workspace/LE01Aug/poky/build/tmp-glibc/work/armv7a-vfp-neon-oemllib32-linux-gnueabi/lib32-pulseaudio/6.Parsing
> configuration file '/home/root/.config/pulse/client.conf'
> I:
> [pulseaudio][/local/mnt/workspace/LE01Aug/poky/build/tmp-glibc/work/armv7a-vfp-neon-oemllib32-linux-gnueabi/lib32-pulseaudio/6.Daemon
> startup successful.
> / # pacmd list
> Daemon not responding.
pacmd doesn't work when pulseaudio is running in the system mode. Use
pactl instead. The difference between the two programs is that pactl
uses the normal method of speaking to the server and pactl uses a weird
method. pactl supports almost everything that pacmd does, and pactl is
in general recommended over pacmd.
>
> Additional info.
>
> / # ps aux | grep -i pulse
> 2228 root 0:07 pulseaudio
> 2242 pulse 0:00 pulseaudio -D --system
> 2312 root 0:00 {grep} /bin/busybox /bin/grep -i pulse
So you've managed to start pulseaudio as a per-user instance for root,
and another instance is running in the system mode. There should be
only one instance running. Which mode do you want to use? If you don't
know, probably the system mode is the right choice.
--
Tanu
https://www.patreon.com/tanuk
