Comment 42 for bug 1773167

Revision history for this message
In , Tanu Kaskinen (tanuk) wrote :

Sorry for the delay in replying...

(In reply to PhilS from comment #35)
> I'm afraid that I don't know the difference between ~/.etc/pulse/ and
> /etc/pulse/.

Ok, so you don't know what "~" means? It's an abbreviation for the home directory. If your username is "phils", then "~/.config/pulse/" is expanded to "/home/phils/.config/pulse/".

> I just used the same syntax as used in the request to provide a log.
>
> I only know that if I start from root then drill down to etc and then pulse
> I can find the client.conf file.
>
> ps aux | grep pulse returns the following:
>
> 275 root 0:00 /usr/bin/pulseaudio --system
> 817 root 0:00 grep pulse

Ok, you're running pulseaudio in the system mode. I had a look at how LibreELEC configures PulseAudio, and it seems to use systemd to start it, so run "systemctl stop pulseaudio" as root. Then run "pulseaudio --system -vv" as root and continue according to my earlier instructions to get the log.

I'm not sure this is a PulseAudio issue, though. LibreELEC seems to disable PulseAudio's ALSA functionality, so I would expect that on LibreELEC you're not supposed to use PulseAudio at all to play to HDMI. Maybe PulseAudio is used only for bluetooth output.