No sound / no audio since qubes-audio*-4.1.25 update

User Support
1

Neither analog output or HDMI or displayport sound works after updating some Qubes packages earlier this week.


qubes-gui-dom0-4.1.25-1.fc32.x86_64           Tue 25 Oct 2022 07:08:42 PM CDT
qubes-core-admin-client-4.1.25-1.fc32.noarch  Tue 25 Oct 2022 07:08:42 PM CDT
python3-qasync-0.23.0-2.fc32.noarch           Tue 25 Oct 2022 07:08:42 PM CDT
linux-firmware-20220913-135.fc32.noarch       Tue 25 Oct 2022 07:08:09 PM CDT
qubes-gui-daemon-4.1.25-1.fc32.x86_64         Tue 25 Oct 2022 07:08:08 PM CDT
qubes-audio-dom0-4.1.25-1.fc32.x86_64         Tue 25 Oct 2022 07:08:08 PM CDT
qubes-audio-daemon-4.1.25-1.fc32.x86_64       Tue 25 Oct 2022 07:08:08 PM CDT
python3-qubesadmin-4.1.25-1.fc32.noarch       Tue 25 Oct 2022 07:08:08 PM CDT
linux-firmware-whence-20220913-135.fc32.noarch Tue 25 Oct 2022 07:08:08 PM CDT

Downgraded the Dom0 kernel to

Linux dom0 5.16.18-2.fc32.qubes.x86_64 #1 SMP PREEMPT Fri Apr 1 22:28:01 CEST 2022 x86_64 x86_64 x86_64 GNU/Linux

and the vm kernel to

Linux browsing 5.16.18-2.fc32.qubes.x86_64 #1 SMP PREEMPT Fri Apr 1 22:28:01 CEST 2022 x86_64 GNU/Linux

after reading reports of audio issues with kernels => 5.6.17

Have tried multiple reboots and changing the source device in Pulseaudio

inxi -Ax shows

Audio:
  Device-1: Intel Tiger Lake-H HD Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 
  Sound Server-1: ALSA v: k5.16.18-2.fc32.qubes.x86_64 running: yes 
  Sound Server-2: PulseAudio v: 14.0-rebootstrapped running: yes

pavucontrol runs and appears to work normally, can see which VMs are playing audio, but there is no sound output whether HDMI or analog.

2

Can someone close this please? Sound did work after the downgrade to 5.16, but I hadn’t realized the wrong output was selected in Pulseaudio.

I am running kernel-latest and what worked to downgrade was

rpm -qa |grep kernel

then removing like

sudo rpm -e kernel-latest-5.18.9-1.fc32.qubes.x86_64

3

Even if it would possible, I wouldn’t delete this. If it happened to you, it might happen to others to overlook such trivial things. So, I’m finding this very valuable.

1 Like
4

I’m having the same issue.
I usually run
$rm -r .config/pulse/*
$pulseaudio -k (it will restart itself)
a couple of times to make it work.
It might turn off again a few times, but sometimes it works for the rest of the session.