On Thu, 2022-09-22 at 12:35 -0700, stan via users wrote:
On Tue, 20 Sep 2022 11:00:13 +0200 andreas.fournier@runbox.com wrote:
On Tue, 2022-09-20 at 10:38 +0200, fedora wrote:
Don't you need to start pipewire as the normal user? i.e.
[host@non-root-user]$ systemctl restart pipewire-pulse.service --user
ah, right. When run as a normal user that command succeeds and in the log I can find
systemd[2290]: Stopping pipewire-pulse.service - PipeWire PulseAudio... systemd[2290]: Stopped pipewire-pulse.service - PipeWire PulseAudio. systemd[2290]: Started pipewire-pulse.service
PipeWire PulseAudio. rtkit-daemon[1231]: Successfully made thread 62005 of process 62005 (/usr/bin/pipewire-pulse) owned by '1000' high priority at nice level - 11.rtkit-daemon[1231]: Successfully made thread 62014 of process 62005 (/usr/bin/pipewire-pulse) owned by '1000' RT at priority 20. juno pipewire-pulse[62013]: 536870912
But still no audio.
Also tried 'aplay -D plughw:2,0 <audio file>'. No audio was produced.
This should have worked, if you have a speaker connected to the out port on the on board sound device (the green one).
The audio came back yesterday, but hard to tell what was the culprit. Anyway yesterday I updated every package to the latest from repo and tested different things. I stumbled upon a software called PulseAudio Volume Control and in its Output Devices tab I fiddled with its knobs and suddenly the audio was back.
One thing that might also play into this is that the OS shows two output devices, when in reality I only have one monitor with built-in speakers that I've been using since always. Settings -> Sound shows two output devices, both named HDMI/DisplayPort - Built-in Audio. PulseAudio Volume Control shows Built-in Audio Digital Stereo (HDMI) twice.
Thanks for all the help