Bluetooth Headset stopped working after update

Ask Fedora
1

My bluetooth headset stopped working after update. I updated fedora and now my bluetooth headset doesn’t work. (It used to work with the a2dp sbc codec. Now it doesn’t work. I suspect it is something to do with pipewire. My headphones are boat rockerz 550.

inxi -fzxx

System:
  Kernel: 6.15.6-200.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
  Console: pty pts/2 wm: kwin_wayland DM: SDDM Distro: Fedora Linux 42 (KDE
    Plasma Desktop Edition)
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop E410KA_E410KA
    v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: E410KA v: 1.0 serial: <filter> UEFI: American
    Megatrends LLC. v: E410KA.322 date: 02/07/2025
Battery:
  ID-1: BAT0 charge: 31.3 Wh (100.0%) condition: 31.3/42.1 Wh (74.4%)
    volts: 11.8 min: 11.8 model: ASUSTeK ASUS Battery serial: N/A
    status: not charging
CPU:
  Info: quad core model: Intel Pentium Silver N6000 bits: 64 type: MCP
    arch: Alder Lake rev: 0 cache: L1: 256 KiB L2: 1.5 MiB L3: 4 MiB
  Speed (MHz): avg: 801 min/max: 800/3300 cores: 1: 801 2: 801 3: 801 4: 801
    bogomips: 8908
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel JasperLake [UHD Graphics] vendor: ASUSTeK driver: i915
    v: kernel arch: Gen-11 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:4e71
  Device-2: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-4:3 chip-ID: 13d3:56e6
  Display: unspecified server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: eDP-1 model: BOE Display 0x07f6 res: 1920x1080 hz: 60 dpi: 158
    diag: 355mm (14")
  API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
    drv: iris surfaceless: drv: iris x11: drv: iris inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.4 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics (JSL)
    device-ID: 8086:4e71
  API: Vulkan v: 1.4.313 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa intel device-ID: 8086:4e71 device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: gputop, intel_gpu_top, lsgpu
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Jasper Lake HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:4dc8
  API: ALSA v: k6.15.6-200.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.6 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
    vendor: AzureWave driver: ath10k_pci v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:0042
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks driver: btusb v: 0.8 type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 bus-ID: 1-8:4 chip-ID: 13d3:3496
  Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 4.2 lmp-v: 8
Drives:
  Local Storage: total: 238.47 GiB used: 17.36 GiB (7.3%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN530
    SDBPNPZ-256G-1002 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4
    serial: <filter> temp: 35.9 C
Partition:
  ID-1: / size: 236.89 GiB used: 17.03 GiB (7.2%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 317 MiB (32.6%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 236.89 GiB used: 17.03 GiB (7.2%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 7.53 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2
    file: /swap/swapfile
Sensors:
  System Temperatures: cpu: 65.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 0
Info:
  Memory: total: 8 GiB available: 7.53 GiB used: 3.03 GiB (40.2%) igpu: 64 MiB
  Processes: 273 Power: uptime: 23m wakeups: 0 Init: systemd v: 257
    target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 32
    Compilers: gcc: 15.1.1 Shell: Sudo v: 1.9.17p1 running-in: konsole
    inxi: 3.3.38

the last 25 lines of journalctl

Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.326] [WRN] PwPipelineManager::on_core_error: Remote error res: No such file or directory
Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.326] [WRN] PwPipelineManager::on_core_error: Remote error message: unknown resource 67 op:2
Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.327] [WRN] PwPipelineManager::on_core_error: Remote error res: No such file or directory
Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.327] [WRN] PwPipelineManager::on_core_error: Remote error message: unknown resource 67 op:2
Jul 19 11:39:37 fedora kded6[13087]: org.kde.pulseaudio: No object for name "bluez_output.FC_58_FA_F3_F6_FD.1"
Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.338] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 0, default.audio.sink, Spa:String:JSON, {"name":"alsa_output.pci-0000_00_1f.3.analog-stereo"}
Jul 19 11:39:37 fedora plasmashell[13132]: org.kde.pulseaudio: No object for name "bluez_input.FC:58:FA:F3:F6:FD"
Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.339] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 0, default.audio.source, Spa:String:JSON, {"name":"alsa_input.pci-0000_00_1f.3.analog-stereo"}
Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.339] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: new default output sink: alsa_output.pci-0000_00_1f.3.analog-stereo
Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.342] [DBG] PwBasePlugin::connect_to_pw: @PwJamesDspPlugin: JamesDsp successfully connected to PipeWire graph
Jul 19 11:39:37 fedora flatpak[13596]: [11:39:37.346] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: output device has changed to: alsa_card.pci-0000_00_1f.3 via route analog-output-speaker
Jul 19 11:39:37 fedora plasmashell[13132]: org.kde.pulseaudio: No object for name "bluez_output.FC_58_FA_F3_F6_FD.1"
Jul 19 11:39:37 fedora plasmashell[13132]: org.kde.pulseaudio: No object for name "bluez_input.FC:58:FA:F3:F6:FD"
Jul 19 11:39:43 fedora bluetoothd[773]: profiles/audio/avctp.c:avctp_control_confirm() Control: Refusing unexpected connect
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.157] [DBG] PwPipelineManager::on_registry_global: Audio/Sink 79 bluez_output.FC_58_FA_F3_F6_FD.1 with serial 547 has been added
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.157] [DBG] PwPipelineManager::on_registry_global: Audio/Source 114 bluez_input.FC:58:FA:F3:F6:FD with serial 548 has been added
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.157] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: device bluez_card.FC_58_FA_F3_F6_FD has changed its output route to: headset-output
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.205] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 0, default.audio.sink, Spa:String:JSON, {"name":"bluez_output.FC_58_FA_F3_F6_FD.1"}
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.205] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 0, default.audio.source, Spa:String:JSON, {"name":"bluez_input.FC:58:FA:F3:F6:FD"}
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.205] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: new default output sink: bluez_output.FC_58_FA_F3_F6_FD.1
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.205] [DBG] FilterContainer::disconnect_filters: disconnecting the JamesDsp filter from PipeWire
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.210] [DBG] PwBasePlugin::connect_to_pw: @PwJamesDspPlugin: JamesDsp successfully connected to PipeWire graph
Jul 19 11:39:44 fedora flatpak[13596]: [11:39:44.215] [DBG] PipewireAudioService::PipewireAudioService$ctor::<lambda>: output device has changed to: bluez_card.FC_58_FA_F3_F6_FD via route headset-output
Jul 19 11:39:44 fedora kernel: input: Rockerz 550 (AVRCP) as /devices/virtual/input/input21
Jul 19 11:39:44 fedora systemd-logind[788]: Watching system buttons on /dev/input/event16 (Rockerz 550 (AVRCP))
2

Do you have way to confirm that the headphones are still in working order?

When reporting a problem, it is most effective if you provide enough detail to allow others with similar hardware to reproduce your issue. Since other users will be reluctant to downgrade, that means making sure you have current Fedora and vendor firmware updates. If you run inxi -Fzxx in a terminal, you will get a succinct text description of your hardware an the drivers being used. Post this as pre-formatted text (use the </> button from the top line of the text entry panel). This will often be found with web searches by others with the same issue, and often helps find a solution.

You can also use journalctl in a terminal to look for error messages related to your issue. If you are not familiar with journalctl, see https://linuxhandbook.com/journalctl-command/. Since journalctl collects massive detail, it does take some effort to isolate the revelvant records using “filter” options.

3

Ok. Just 10 minutes.

4

You appear to be using the flatpak version of JamesDSP for Linux Open-source sound effects for PipeWire and PulseAudio. Fedora lists version 2.7.0, which has not been updated for a year. If so, you should post a report at https://github.com/Audio4Linux/JDSP4Linux/issues. There are other posts requesting updates.

Meanwhile, you should try to use your headset with Fedora packages.