Bug 2383611 - Bluetooth speaker connected over A2DP, but no audio output from kernel 6.15.5 onwards
Summary: Bluetooth speaker connected over A2DP, but no audio output from kernel 6.15.5...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-26 05:58 UTC by RonBis
Modified: 2025-07-27 18:46 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description RonBis 2025-07-26 05:58:25 UTC
1. Please describe the problem:
After updating to kernel version 6.15.5-200.fc42.x86_64, my Tribit XSound Go Bluetooth speaker no longer outputs any audio when connected using the A2DP (Advanced Audio Distribution Profile).

The device connects successfully, and PipeWire detects it correctly as an a2dp-sink with codec sbc. It appears as the selected output in GNOME Settings, and audio playback begins in applications (e.g., videos play, progress bars move), but no sound is emitted from the speaker.

This only affects A2DP mode. When switching to HSP/HFP (handsfree) mode, audio is output to the speaker normally, albeit at lower quality.

This issue only affects this specific Bluetooth device. Other devices, such as Bluetooth earbuds, work correctly over A2DP on the same system, kernel, and user configuration. Additionally, this speaker works perfectly in kernel 6.15.4, confirming a regression.

In pw-cli (PipeWire), the node is shown as active, in the “running” state, with 2 input ports and 0 output ports, indicating a possible issue with audio routing or port configuration at the driver or kernel level. The node’s media class is Audio/Sink, and profile a2dp-sink is correctly set.

No useful output is observed in pw-mon or pw-dump for this node when attempting playback in the broken kernel versions.

A suspicious message appears in dmesg on kernels 6.15.5 and above:
`Bluetooth: hci0: SCO packet for unknown connection handle 257`

2. What is the Version-Release number of the kernel:
Affected:

    kernel-6.15.5-200.fc42.x86_64

    kernel-6.15.6-200.fc42.x86_64

    kernel-6.15.7-200.fc42.x86_64

Working:

    kernel-6.15.4-200.fc42.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?
Yes, A2DP audio on this speaker worked reliably in kernel 6.15.4-200.fc42.

The issue first appeared in:

    kernel-6.15.5-200.fc42.x86_64


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes, the issue is consistently reproducible on the same hardware.

Steps:

    Boot into kernel 6.15.5 or later.

    Use GNOME or bluetoothctl to connect to the Tribit XSound Go speaker.

    Verify it connects with profile a2dp-sink and codec sbc.

    Play any media (e.g., a YouTube video or system sounds).

    Observe: no sound is heard, although playback continues as if normal.

    Switch profile to headset-head-unit (HSP/HFP): audio plays.

    Reboot into 6.15.4: audio works again in A2DP with no intervention.

5. Does this problem occur with the latest Rawhide kernel?
Rawhide not yet tested. I will do so and update this report if necessary.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
Yes. The system is using nvidia-akmods from RPM Fusion for NVIDIA GPU support. However, this issue affects Bluetooth audio and occurs regardless of whether the NVIDIA driver is active or not. The problem is reproducible even in fallback sessions with software rendering or when the discrete GPU is unused.

7. Please attach the kernel logs.
Working kernel log (kernel-6.15.4-200.fc42.x86_64)

> sudo dmesg | grep -iE 'bluetooth|btusb|a2dp|hci'
[    1.073907] ahci 0000:06:00.0: version 3.0
[    1.074051] ahci 0000:06:00.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[    1.074055] ahci 0000:06:00.0: 1/1 ports implemented (port mask 0x1)
[    1.074058] ahci 0000:06:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
[    1.074286] scsi host0: ahci
[    1.074487] ahci 0000:06:00.1: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[    1.074491] ahci 0000:06:00.1: 1/1 ports implemented (port mask 0x1)
[    1.074493] ahci 0000:06:00.1: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
[    1.074688] scsi host1: ahci
[    1.075152] xhci_hcd 0000:05:00.3: xHCI Host Controller
[    1.075209] xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 1
[    1.075302] xhci_hcd 0000:05:00.3: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
[    1.075582] xhci_hcd 0000:05:00.3: xHCI Host Controller
[    1.075623] xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 2
[    1.075626] xhci_hcd 0000:05:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[    1.075702] usb usb1: Product: xHCI Host Controller
[    1.075704] usb usb1: Manufacturer: Linux 6.15.4-200.fc42.x86_64 xhci-hcd
[    1.076166] usb usb2: Product: xHCI Host Controller
[    1.076168] usb usb2: Manufacturer: Linux 6.15.4-200.fc42.x86_64 xhci-hcd
[    1.076563] xhci_hcd 0000:05:00.4: xHCI Host Controller
[    1.076604] xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 3
[    1.076679] xhci_hcd 0000:05:00.4: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
[    1.076953] xhci_hcd 0000:05:00.4: xHCI Host Controller
[    1.076987] xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 4
[    1.076991] xhci_hcd 0000:05:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    1.077041] usb usb3: Product: xHCI Host Controller
[    1.077043] usb usb3: Manufacturer: Linux 6.15.4-200.fc42.x86_64 xhci-hcd
[    1.077496] usb usb4: Product: xHCI Host Controller
[    1.077498] usb usb4: Manufacturer: Linux 6.15.4-200.fc42.x86_64 xhci-hcd
[    1.311430] usb 3-3: new high-speed USB device number 2 using xhci_hcd
[    1.311465] usb 1-2: new full-speed USB device number 2 using xhci_hcd
[    1.653422] usb 1-4: new full-speed USB device number 3 using xhci_hcd
[    9.590893] Bluetooth: Core ver 2.22
[    9.590995] NET: Registered PF_BLUETOOTH protocol family
[    9.590998] Bluetooth: HCI device and connection manager initialized
[    9.591004] Bluetooth: HCI socket layer initialized
[    9.591008] Bluetooth: L2CAP socket layer initialized
[    9.591015] Bluetooth: SCO socket layer initialized
[    9.643527] usbcore: registered new interface driver btusb
[    9.644983] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[    9.646996] Bluetooth: hci0: Device revision is 1
[    9.647003] Bluetooth: hci0: Secure boot is enabled
[    9.647006] Bluetooth: hci0: OTP lock is enabled
[    9.647008] Bluetooth: hci0: API lock is enabled
[    9.647010] Bluetooth: hci0: Debug lock is disabled
[    9.647012] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    9.691466] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[    9.691488] Bluetooth: hci0: Boot Address: 0x24800
[    9.691491] Bluetooth: hci0: Firmware Version: 193-33.24
[   11.063947] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.063952] Bluetooth: BNEP filters: protocol multicast
[   11.063957] Bluetooth: BNEP socket layer initialized
[   11.212819] Bluetooth: hci0: Waiting for firmware download to complete
[   11.212945] Bluetooth: hci0: Firmware loaded in 1485809 usecs
[   11.213021] Bluetooth: hci0: Waiting for device to boot
[   11.227971] Bluetooth: hci0: Device booted in 14644 usecs
[   11.230290] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[   11.235997] Bluetooth: hci0: Applying Intel DDC parameters completed
[   11.238994] Bluetooth: hci0: Firmware revision 0.3 build 193 week 33 2024
[   11.245032] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[   11.412554] Bluetooth: MGMT ver 1.23
[   21.322786] Bluetooth: RFCOMM TTY layer initialized
[   21.322803] Bluetooth: RFCOMM socket layer initialized
[   21.322823] Bluetooth: RFCOMM ver 1.11
-----------------------------------------------------------------------------------
Problematic kernel log (kernel-6.15.7-200.fc42.x86_64)
> sudo dmesg | grep -iE 'bluetooth|btusb|a2dp|hci'
[    1.071979] ahci 0000:06:00.0: version 3.0
[    1.072136] ahci 0000:06:00.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[    1.072140] ahci 0000:06:00.0: 1/1 ports implemented (port mask 0x1)
[    1.072142] ahci 0000:06:00.0: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
[    1.072426] scsi host0: ahci
[    1.072629] ahci 0000:06:00.1: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[    1.072633] ahci 0000:06:00.1: 1/1 ports implemented (port mask 0x1)
[    1.072635] ahci 0000:06:00.1: flags: 64bit ncq sntf ilck pm led clo only pmp fbs pio slum part 
[    1.072881] scsi host1: ahci
[    1.073372] xhci_hcd 0000:05:00.3: xHCI Host Controller
[    1.073412] xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 1
[    1.073503] xhci_hcd 0000:05:00.3: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
[    1.073784] xhci_hcd 0000:05:00.3: xHCI Host Controller
[    1.073825] xhci_hcd 0000:05:00.3: new USB bus registered, assigned bus number 2
[    1.073828] xhci_hcd 0000:05:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[    1.073907] usb usb1: Product: xHCI Host Controller
[    1.073909] usb usb1: Manufacturer: Linux 6.15.7-200.fc42.x86_64 xhci-hcd
[    1.074387] usb usb2: Product: xHCI Host Controller
[    1.074389] usb usb2: Manufacturer: Linux 6.15.7-200.fc42.x86_64 xhci-hcd
[    1.074772] xhci_hcd 0000:05:00.4: xHCI Host Controller
[    1.074813] xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 3
[    1.074889] xhci_hcd 0000:05:00.4: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
[    1.075159] xhci_hcd 0000:05:00.4: xHCI Host Controller
[    1.075209] xhci_hcd 0000:05:00.4: new USB bus registered, assigned bus number 4
[    1.075218] xhci_hcd 0000:05:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[    1.075314] usb usb3: Product: xHCI Host Controller
[    1.075316] usb usb3: Manufacturer: Linux 6.15.7-200.fc42.x86_64 xhci-hcd
[    1.076373] usb usb4: Product: xHCI Host Controller
[    1.076375] usb usb4: Manufacturer: Linux 6.15.7-200.fc42.x86_64 xhci-hcd
[    1.312598] usb 3-3: new high-speed USB device number 2 using xhci_hcd
[    1.312670] usb 1-2: new full-speed USB device number 2 using xhci_hcd
[    1.650492] usb 1-4: new full-speed USB device number 3 using xhci_hcd
[    9.866316] Bluetooth: Core ver 2.22
[    9.866362] NET: Registered PF_BLUETOOTH protocol family
[    9.866477] Bluetooth: HCI device and connection manager initialized
[    9.866485] Bluetooth: HCI socket layer initialized
[    9.866489] Bluetooth: L2CAP socket layer initialized
[    9.866499] Bluetooth: SCO socket layer initialized
[   10.225000] usbcore: registered new interface driver btusb
[   10.227162] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[   10.229157] Bluetooth: hci0: Device revision is 1
[   10.229162] Bluetooth: hci0: Secure boot is enabled
[   10.229164] Bluetooth: hci0: OTP lock is enabled
[   10.229167] Bluetooth: hci0: API lock is enabled
[   10.229168] Bluetooth: hci0: Debug lock is disabled
[   10.229170] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   10.268655] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[   10.268696] Bluetooth: hci0: Boot Address: 0x24800
[   10.268698] Bluetooth: hci0: Firmware Version: 193-33.24
[   11.464111] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.464116] Bluetooth: BNEP filters: protocol multicast
[   11.464123] Bluetooth: BNEP socket layer initialized
[   11.806898] Bluetooth: hci0: Waiting for firmware download to complete
[   11.807151] Bluetooth: hci0: Firmware loaded in 1502425 usecs
[   11.807291] Bluetooth: hci0: Waiting for device to boot
[   11.822197] Bluetooth: hci0: Device booted in 14629 usecs
[   11.825046] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[   11.831252] Bluetooth: hci0: Applying Intel DDC parameters completed
[   11.834269] Bluetooth: hci0: Firmware revision 0.3 build 193 week 33 2024
[   11.840533] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[   12.021220] Bluetooth: MGMT ver 1.23
[   21.804512] Bluetooth: RFCOMM TTY layer initialized
[   21.804528] Bluetooth: RFCOMM socket layer initialized
[   21.804538] Bluetooth: RFCOMM ver 1.11
[   85.889563] Bluetooth: hci0: SCO packet for unknown connection handle 257
[  222.048560] Bluetooth: hci0: SCO packet for unknown connection handle 257
[  782.604536] Bluetooth: hci0: SCO packet for unknown connection handle 257
[ 1125.175512] Bluetooth: hci0: SCO packet for unknown connection handle 257
[ 1125.175521] Bluetooth: hci0: SCO packet for unknown connection handle 257
[ 1262.736470] usb 1-2: new full-speed USB device number 4 using xhci_hcd
[19427.603650] usb 3-3: reset high-speed USB device number 2 using xhci_hcd
[19427.614712] usb 1-2: reset full-speed USB device number 4 using xhci_hcd
[19427.910526] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[19429.038662] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[19429.040708] Bluetooth: hci0: Device revision is 1
[19429.040722] Bluetooth: hci0: Secure boot is enabled
[19429.040729] Bluetooth: hci0: OTP lock is enabled
[19429.040735] Bluetooth: hci0: API lock is enabled
[19429.040741] Bluetooth: hci0: Debug lock is disabled
[19429.040747] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[19429.041994] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[19429.042079] Bluetooth: hci0: Boot Address: 0x24800
[19429.042087] Bluetooth: hci0: Firmware Version: 193-33.24
[19430.731826] Bluetooth: hci0: Waiting for firmware download to complete
[19430.732714] Bluetooth: hci0: Firmware loaded in 1651074 usecs
[19430.732799] Bluetooth: hci0: Waiting for device to boot
[19430.747709] Bluetooth: hci0: Device booted in 14627 usecs
[19430.747775] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[19430.753770] Bluetooth: hci0: Applying Intel DDC parameters completed
[19430.756749] Bluetooth: hci0: Firmware revision 0.3 build 193 week 33 2024
[19430.762784] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[19430.930479] Bluetooth: MGMT ver 1.23
[32667.410446] usb 3-3: reset high-speed USB device number 2 using xhci_hcd
[32667.608469] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[32668.750570] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[32668.752538] Bluetooth: hci0: Device revision is 1
[32668.752548] Bluetooth: hci0: Secure boot is enabled
[32668.752553] Bluetooth: hci0: OTP lock is enabled
[32668.752558] Bluetooth: hci0: API lock is enabled
[32668.752563] Bluetooth: hci0: Debug lock is disabled
[32668.752567] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[32668.790868] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[32668.790889] Bluetooth: hci0: Boot Address: 0x24800
[32668.790891] Bluetooth: hci0: Firmware Version: 193-33.24
[32670.297747] Bluetooth: hci0: Waiting for firmware download to complete
[32670.298574] Bluetooth: hci0: Firmware loaded in 1472357 usecs
[32670.298718] Bluetooth: hci0: Waiting for device to boot
[32670.313595] Bluetooth: hci0: Device booted in 14581 usecs
[32670.317219] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[32670.322655] Bluetooth: hci0: Applying Intel DDC parameters completed
[32670.326148] Bluetooth: hci0: Firmware revision 0.3 build 193 week 33 2024
[32670.332072] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[32670.498925] Bluetooth: MGMT ver 1.23
[34464.300471] Bluetooth: hci0: SCO packet for unknown connection handle 257

Reproducible: Always

Comment 1 old-attic-breeches 2025-07-27 03:49:49 UTC
This is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=2381852

Comment 2 old-attic-breeches 2025-07-27 18:46:33 UTC
I installed Kernel 6.15.8 from koji and the issue is fixed there, so this should be resolved once that officially hits Fedora.


Note You need to log in before you can comment on or make changes to this bug.