Gordon Messmer writes:
On 11/16/21 15:27, Sam Varshavchik wrote:
> So, anyone knows how to set the permanent default output device?
A search for "pipewire set persistent default" brings up a few discussions
suggesting that pipewire *should* save the default across sessions, but that
was broken in 0.3.33, and then fixed, and might be broken again.
Well, it is persistent across sessions. If I log out and back in the default
audio stays put, only a reboot resets it. I installed the latest pipewire
update, 0.3.40, no difference.
My eye caught a "Manage Sound Card State (restore and store)" service
getting started on boot. I tracked it down to alsa-state.service, and this
is what "systemctl status alsa-state.service" shows me:
Nov 18 06:59:56
monster.email-scan.com systemd[1]: Started Manage Sound Card
State (restore and store).
Nov 18 06:59:56
monster.email-scan.com alsactl[3624]: alsactl 1.2.5.1 daemon
started
Nov 18 06:59:56
monster.email-scan.com alsactl[3624]: alsa-lib parser.c:242:
(error_node) UCM is not supported for this HDA model (HDA Intel at
0xfa9f8000 irq 47)
Nov 18 06:59:56
monster.email-scan.com alsactl[3624]: alsa-lib main.c:1405:
(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration
-6
Nov 18 06:59:56
monster.email-scan.com alsactl[3624]: alsa-lib main.c:1405:
(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration
-2
This looks relevant, but I don't grok it. "systemctl stop" and
"start" logs
this again. Looks relevant enough to create an alsa-utils issue on github
and see what they say.