some time ago, I installed the Fedora 32 TemplateVM via sudo qubes-dom0-update qubes-template-fedora-32 as stated in the documentation.
Since then I used it mainly for NetVMs. Recently I tried to use it for different purposes (e.g. as a DVM for disposable qubes) and recognized that I am not able to play sound whatsoever in any Fedora-based qube.
When running pavucontrol in dom0 I only get a list of all running, Debian-based qubes on the tab Playback for which the sound works fine.
Can anyone think of a reason or even a solution for this? Did you have similar issues with Fedora-based qubes?
Same here for me and what I understand - itās a worldwide issue. This means, it shouldnāt work for anyone (with 4.0.3 or 4.0.4) and Fedora-32 templates/VMs at the time.
Am I correct?
There isnāt any solution at the time and I hope it will be fixed within the next coming updatesā¦
For the time being, Iām doing all my āsound-stuffā with the Debian-10 template/VMs.
Thank you for pointing me to that post. I donāt think that my issue is related, since it seems to be a problem for all qubes (from what I get, reading the post) - maybe even on kernel level - and on the other hand, sound on my Debian templates works fine.
Nevertheless, I donāt know for sure, but a clean reinstall (what fixed the problem in the other post) is not possible atm.
Thank you for your reply!
Since it seems to be a general issue and not just bad configuration on my side, Iāll open a bug ticket.
Iāll keep you posted!
Is pulseaudio-qubes installed in your template? To find out, you can run rpm -qa | grep pulseaudio-qubes in any VM based on it.
If it is, you can try to reinstall the fedora template to see if the problem occurs for a fresh template. Then you can update it, and see if it breaks then.
@TheGardener Over at GitHub, donob4n gave me the solution:
Try to run sudo dnf install pulseaudio-qubes in your Fedora template(s). This seems to be some kind of interface necessary for pulseaudio to work within qubes.
I donāt get why itās not already within our Fedora templates, but Iām glad itās solved.
Do you know, when you installed your Fedora 32 templates by any chance?
Maybe there was a time when the pulseaudio-qubes package was missing in the reposā¦
Glad itās solved can you mark post that solved the issue as the āsolutionā.
You do this by clicking the at the bottom of the post and then āSolutionā. This way when people see your post, they can be taken right to the solution
@TheGardner I did - it just didnāt seem right to mark my own answer as solution ^^
@Rooftop Thatās interesting - As I stated over at GitHub, I guess I installed around November 2020. Certainly possible that they fixed the package in the meantime and TheGardner and me just had bad timing
From reading other threads, what has happened to a lot of people was that they forcefully updated, which included the removal of a conflicting version of pulseaudio-qubes, when there was a conflict of package versions at some point. This occasionally happens with pulseaudio, when Qubes canāt keep up.
Iām not saying that this is what you did. There may be another issue that leads to this as well.