AppVMs stop connecting to sys-audio after some time (r4.3-rc2)

User Support
1

Has anyone come across this issue before? After some time (days) of having my r4.3-rc2 installation running, new qubes stop connecting to sys-audio, they don’t show up in pasystray or pavucontrol.

This did not happen on r4.2.

Any ideas for what could be causing this? Logs to get? (Journalctl doesn’t seem to have too much interesting info). Ideas for getting this to work, somehow reconnecting the qubes to sys-audio?

1 Like
2

Try to restart the pipewire in the qubes:

$ systemctl --user restart pipewire
3

Sadly, did not work. Also tried it in sys-audio itself, which successfully disconnected all the other qubes that used to work, so no audio for me :frowning: (until next reboot).

4

Restarting sys-audio fixes the issue. Still does not help to know what causes it, though.

1 Like
5

If anyone else has the same problem, here’s a workaround that restarts sys-audio every night.

Add this to your user’s crontab in dom0 (crontab -e):

15 04 * * * bash -c "qvm-shutdown sys-audio --force; sleep 5; qvm-start sys-audio"
6

Nitpicking: “sleep 5” is a gamble or a waste of time; you can use “–wait” with qvm-shutdown, and skip the sleep:
15 04 * * * bash -c "qvm-shutdown --wait --force sys-audio; qvm-start sys-audio"

1 Like
7

I’ve seen somewhere that pipewire server have 10 connected clients/qubes limit (dunno if it’s pipewire or qubes os limit).
So maybe you exceeding this limit somehow?
I have only 3 qubes set to use audiovm = sys-audio in qvm-prefs. The rest are set to none.

1 Like