Check the logs with
$ sudo journalctl --unit bluetooth.service
Thay may give you some information on what is going on. I have found that, running a disposable sys-audio, sometimes I need to start the blueman-manager twice to get it to work.
Regarding the persistence of bluetooth pairings, it may be a good idea to add a link to the documentation on bind-dirs, to do a bind-mount of /var/lib/bluetooth (or the instructions to do that).
Edit: Fixed a typo!
After checking it seems it started but there were some errors about connection failures but I believe this was with my error attempt to connect using the other bluetooth USB device and not the integrated one. The last message states that Battery Provider manager destroyed.
Bluetooth adapter doesnât load at all.
check dmesg, look for anything related to usb error.
you could first launch blueman-manager from sys-usb before passing the USB device, just to see if it work
I get the error Failed to connect to bus: No medium found. Then I get No adapters found.
No USB errors that I can see.
I connected the speaker via USB cable to the laptop. I can see the device under sys-usb. I can successfully attach the device to sys-audio however I donât see the speaker in sys-audio. What am I missing?
Replying to myself to keep a record here (in case someone bumps into this problem). This is pipewire problem, not a hardware one. In my case, it seems to be solved by upgrading the pipewire packages in sys-audio to the bookworm-backports version (1.2.7) in Debian 12 (for a debian-based audioVM). Since the Fedora pipewire version is newer than the Debian bookworm one, this may not happen in Fedora-based audioVMs.
1 Like
Hello, I some how lost all sound in my Windows 10 HVM. The notification that I get after I reboot it is attached . I have seen this in a earlier post I have not seen it solved. Any idea of the issue?
Qubes 4.2.4
Denied: admin.vm.property.Get
Denied admin.vm.property.Get+virt_mode from sys-audio to windows10New`
@alimirjamali - thank you very much for this promising news. Can you please provide a link to the update that fixed the issue for you? Eagerly waiting to have it appliedâŚ
Yes. Sure. Links and detailed explanations here.
1 Like
Recently there is problem with high fidelity playback AAC sometimes (no audio) (bluetooth buds). Donât know what is causing it. Qubes 4.2.4 and fedora 41 minimal sys-audio. Codec mSBC works every time.
After a long time running just fine, my sys-audio qube has stopped working. Now, none of my app qubes has sound. The sys-audio qube is fedora-40 based.
In sys-audio:
user@sys-audio ~]$ lspci -v
...
00:06.0 Audio device: Intel Corporation Comet Lake PCH cAVS
Subsystem: Hewlett-Packard Company Device 8742
Physical Slot: 6
Flags: bus master, fast devsel, latency 64, IRQ 40
Memory at f2110000 (64-bit, non-prefetchable) [size=16K]
Memory at f2000000 (64-bit, non-prefetchable) [size=1M]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_avs, snd_sof_pci_intel_cnl
00:07.0 Audio device: NVIDIA Corporation Device 10fa (rev a1)
Subsystem: Hewlett-Packard Company Device 8742
Physical Slot: 7
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at f2114000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
Running dmesg says that no codes have been initialized for snd_hda_intel (device 00:06.0):
user@sys-audio ~]$ sudo dmesg | grep snd_hda_intel
[ 2.941200] snd_hda_intel 0000:00:07.0: Disabling MSI
[ 2.958721] snd_hda_intel 0000:00:06.0: spurious response 0x0:0x2, last cmd=0x000000
[ 3.962167] snd_hda_intel 0000:00:06.0: azx_get_response timeout, switching to polling mode: last cmd=0x000f0000
[ 4.962566] snd_hda_intel 0000:00:06.0: No response from codec, disabling MSI: last cmd=0x000f0000
[ 5.995042] snd_hda_intel 0000:00:06.0: Codec #0 probe error; disabling it...
[ 5.995046] snd_hda_intel 0000:00:06.0: no codecs initialized
[user@sys-audio ~]$
alsamixer shows only the HDA NVidia sound card.
pasystray always shows Default Sink is Dummy Output 100% and Default Source is None.
I donât know why the audio has stopped working. And I donât know how to fix it. Could someone help me, please?
TIA
I found the culprit to be the kernel version. It seems there are some sound problems with version 6.12.18. Downgrading to version 6.6.77 fixed the problem.
3 Likes
Iâve been using sys-audio for a while now, and Iâve recently needed to use a mic on a headset for zoom calls. The mic itself is detachable from the headset, but the headset plugs in via a 3.5mm jack. Iâve tried a few different things, like attaching dom0:mic to the qube I want a mic in, but I canât get it to show up in sys-audio (which has the PCIe audio device) or the qube.
Any pointers where I should be looking?
@alimirjamali - thanks for the link. I can see it refers to r4.3. Does it mean people on r4.2 wonât get the fix? Thank you!
Hi. First of all, an update to this. I believe that patch has improved keyboard layout switching a lot but not 100% fixed. I still notice it time to time but rarely. I am not fully certain if the RPC caching patches would come to R4.2 (and when). But the chances is that the r4.2 might get the fixes after some time. Unfortunately this could take a lot of time as sometimes I witness the patches from last summer which are just backported to r4.2
The entire keyboard layout switching mechanism has to go through a review. As it is currently completely broken for KDE on r4.3 (there is an open issue for this on Github).
1 Like
Thank you, looking forward to the fixing. Quite hard to tolerate when it is either audio-qube or usable keyboard switchingâŚ
1 Like