https://bugs.kde.org/show_bug.cgi?id=513536
--- Comment #6 from TSUKUMO Akito <[email protected]> --- (In reply to ledo.kane from comment #3) > (In reply to TSUKUMO Akito from comment #2) > > Comment from original reporter (myself): > > > > I can confirm the same regression in 25.12.1-1. > > Disabling the Bluetooth backend (via Settings > Backends > Bluetooth > > unchecked, or disabled_providers=BluetoothLinkProvider in > > ~/.config/kdeconnect/config) no longer works. > > The interference with PipeWire A2DP audio (choppy/stuttering playback on > > WH-1000XM4) occurs unconditionally after connecting Bluetooth headphones. > > > > Downgrading to 25.08.2-2 completely resolves the issue (stable, no > > stuttering). > > Temporary workaround: Manually restart kdeconnectd after connecting > > headphones, but this is not practical for daily use. > > > > Affected versions: 25.12.1-1 (EndeavourOS) > > Workaround: Pin kdeconnect to 25.08.2-2 with IgnorePkg in pacman.conf > > > > Please prioritize this regression, as it makes Bluetooth audio unusable with > > KDE Connect running. > > Thank you! > > I am also on EndeavourOS but i am on a RPI5 so it is the "arm" version > (based on arch arm, using the same package repository). Are you also on a > RPI? If that is the case, maybe our weak bluetooth chip can't handle > multiple querries and streams at the same time and stalls. But kdeconnect > should not "constantly" querry for bluetooth devices i would assume. I mean > it must stop at some point, but as our experience proves it, it just doesn't. @ledo.kane Thanks for the info and the suggestion. Just to clarify: I'm actually running EndeavourOS on a **MacBook Pro 2018** (Intel x86_64) with the **linux-t2** kernel (not ARM / RPi5). So the weak Bluetooth controller theory might not fully apply here, but it's still interesting that you're seeing the same symptoms on RPi5 (ARM). For me, the issue definitely started/regressed with KDE Connect 25.12 series and is reproducible even when the Bluetooth backend is supposedly disabled (in 25.12.1). Downgrading to 25.08.3-2 or forcing a kdeconnectd restart right after connecting the headset remains the only reliable workarounds so far. Thanks again for testing and reporting — more confirmations from different hardware help a lot. -- You are receiving this mail because: You are watching all bug changes.
