Option to disable detecting bluetooth audio devices

Desktop
1

Hello,

I’m currently suffering a pretty unique issue. So I’m in a public space (university library) surrounded by individuals with bluetooth-capable devices. As a result of this, if I go to look at the available audio output devices in the sound settings screen, I am faced with so many devices that the ui element reaches off the end of laptop screen (see attached images). This is not necessarily a problem, but rather, it is the cause of another much more annoying problem.

Using discord is effectively impossible! Every time I open the client i am bombarded with notifications asking if I want to switch audio devices. Now, a cursory glance through web forums about getting rid of this feature of discord would suggest that you simply click the “don’t notify me about this device again” button. This would work if there were only a few devices, however, I am in an area where an unbounded and unpredictable number of devices are coming and going in range of this godforsaken laptop. So I figured I would go to the source of the problem and disable the audio devices.

If someone would be so kind as to advise me what the best strategy to disable detection of bluetooth devices I would greatly appreciate that. For reference, my laptop is running Fedora 44 Silverblue.

image
image840×1656 103 KB

2

Hi :smiley:

Oh, that’s so many devices :grimacing:

The bulk of the devices listed in your sound output look like AirPlay, not Bluetooth devices. These are discovered by a dedicated module in Pipewire.

Fedora conveniently ships this module as a separate package that you can uninstall: pipewire-config-raop. For Silverblue the uninstall command should be rpm-ostree uninstall pipewire-config-raop (and then of course reboot for the changes to take effect).

3

Thanks for the answer! I didn’t follow the exact solution which you provided (which was to remove the module alltogether), but rather I just disabled that module. As silverblue is designed as an immutable system, i’d rather keep the base system in-tact. Your answer definitley pointed me in the right direction though. For anyone else curious, I came accross this solution to a post which detailed, funnily enough, the exact same problem I was facing. The solution recommends just disabling the module through a user-defined conf file.

Otherwise, thanks!