Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using sys-audio, mod.qubes-audio: no /qubes-audio-domain-xid entry in QubesDB #9722

Open
bi0shacker001 opened this issue Jan 20, 2025 · 1 comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: audio hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.

Comments

@bi0shacker001
Copy link

bi0shacker001 commented Jan 20, 2025

Qubes OS release

Qubes OS 4.2

Brief summary

When launching sys-audio, audio devices are detected properly, vu meters are peaking properly in pavucontrol, but no sound output occurs.
Using ASUS ROG strix laptop on linux kernel 6.11. Audio support functioned properly before systemwide updates.

Steps to reproduce

1.Start sys-audio, then vm with content
2.play content
3.

Expected behavior

Expect audio output from built-in speakers

Actual behavior

No sound output at all (input still works)
journalctl shows:

Jan 20 14:06:05 sys-audio pipewire[1093]: mod.qubes-audio: no /qubes-audio-domain-xid entry in QubesDB
Jan 20 14:06:05 sys-audio pipewire[1093]: mod.qubes-audio: unknown peer domain, cannot create stream
Jan 20 14:06:05 sys-audio pipewire[1093]: mod.qubes-audio: unknown peer domain, cannot create stream
@bi0shacker001 bi0shacker001 added the P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. label Jan 20, 2025
@andrewdavidwong andrewdavidwong added needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. C: audio affects-4.2 This issue affects Qubes OS 4.2. labels Jan 21, 2025
@bi0shacker001
Copy link
Author

bi0shacker001 commented Feb 5, 2025

I tried nuking sys-audio, resetting audiovm to dom0, and testing. Speaker output works in dom0.
After recreating sys-audio (using the same template as before), setting audiovm again, and testng, still no sound from the built-in speakers.
Tested with bluetooth audio, sound works over bluetooth, so the issue is purely with the built-in speakers.
Alright, this is probably a device-specific issue, which is weird. This model of laptop has controller CS35L41, which didn't have kernel patches until 6.7 (which I waited for, and when I updated, that fixed the audio the first time). Those patches should still be in the kernel, so I'm not sure what additional troubleshooting I should try

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: audio hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.
Projects
None yet
Development

No branches or pull requests

2 participants