nixos/wireplumber: fix systemwide bluetooth integration

[andrevmatos]

Description of changes

Currrently, trying to connect to a Bluetooth headset with systemWide Pipewire gives this error in bluetooth.service:

src/service.c:btd_service_connect() a2dp-sink profile connect failed for <bt_mac>: Protocol not available

Fix from https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3828#note_2270701
wireplumber<0.5 had this fix in place, but on its format, which got removed in #278760
This PR brings that back

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[K900]

It should have been unloaded automatically... I'll ask upstream.

[andrevmatos]

May have todo with my system using startx/startplasma-wayland-from-terminal, instead of SDDM or other display manager? Either way, tested the fix and it works here

[K900]

That definitely shouldn't affect the system-wide service in any way.

[andrevmatos]

It shouldn't affect the service, but logind sees different seat types for both cases, and this may be affecting bluez's seat monitoring through logind. Either way, the line added here was recommended in the upstream repo, and fixes the issue here.

[andrevmatos]

Meanwhile (for whoever may care), I've fixed it in my system like this:

services.pipewire.wireplumber.configPackages = [
  (pkgs.writeTextDir "share/wireplumber/wireplumber.conf.d/59-systemwide-bluetooth.conf" ''
    wireplumber.profiles = {
      main = {
        monitor.bluez.seat-monitoring = disabled
      }
    }
  '')
];