Dependency Graph
View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007726 | Kali Linux | General Bug | public | 2022-05-21 05:35 | 2022-06-01 07:45 |
Reporter | neyoojhony | Assigned To | daniruiz | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Product Version | kali-dev | ||||
Summary | 0007726: Since updates after 5.5.2022 Bluetooth headsets wont connect anymore | ||||
Description | Since updates from 5.5.2022 bluetooth headsets wont connect anymore. If they are already known, they connect, disconnect, then connect again to finally disconnect. The error message is: br-connection-unknown. If the device was not paired they won't pair and the error message is br-connection-profile-unavailable. | ||||
Steps To Reproduce | Install kali from CD, or USB-Stick. Then upgrade to latest packages. if installing 2022-W18 bluetooth devices won't work right after installing. | ||||
duplicate of | 0007699 | closed | Since updates after 5.5.2022 Bluetooth headsets wont connect anymore |
Hi, please check the version of the package bluez. Open a terminal and type: <pre> The version should be "5.64-2+kali1". We just updated this package last week, and we hope that it should fix the issue. If you have an older version, please update your Kali system (and maybe reboot, just to be sure). Thanks! |
|
<code> Looks good to me. But after rebooting, the bluetooth audio device connects, disconnects, connects, then finally disconnects again if it was paired before. If not, the device is found, but you can not pair it. Error message in the first case: "br-connection-unknown". In the second case: "no device found" -- even if the device was shown in "Bluetooth Devices". <code> Looks like there is some harmful interaction between PipeWire and bluez not building up the sound bridge, or building it, but not noticing it was build successfully, timing out and disconnecting? |
|
What makes you think that? Do you see anything in the log that suggests that? By the way, you should try to run "journalctl -f" in the console to see the system logs in real time, maybe you will understand what happens exactly. It's normal that pipewire is installed, there's nothing wrong with that. There's also pulseaudio on your system, and it's more likely that the issue lies somewhere in pulseaudio or the bluetooth stack. Note that the issue can also be due to the drivers, that are part of the kernel. Did you try to boot an older kernel? It's something that you can select in the Kali boot prompt. |
|
What makes you think that? Do you see anything in the log that suggests that? By the way, you should try to run "journalctl -f" in the console to see the system logs in real time, maybe you will understand what happens exactly. The comments found for the very same bug within xUbuntu 20.04, 21.10 and 22.04. All three stopped connecting to bluetooth audio devices upgrading bluez and pipewire. Right before debian 11.3 stopped connecting them after upgrading bluez only. The pipewire update later on did not help. Installing xUbuntu 22.04 from the static dvd, without upgrading, makes it work again. Upgrading one of pipewire, bluez or pulse-audio kills it again. For Kali it is mainly the same: installing the last working weekly 2022-W18 it works until I upgrade one of pipewire, bluez or pulse-audio. Upgrading all to the latest versions does not help: non of my audio devices will connect, while the do with 2022-W18. |
|
I've tried to get rid of pulse-audio, but only managed to kill the whole bluetooth audio stack. Without pulse-audio none of the installed bluez tools will even recognize audio. Even after following various howtos replacing pulse-audio with pipewire. |
|
I've thought this first, but trying with only upgrading kernels and drivers did nothing to bluetooth audio devices. They even work with the latest kernel upgrades or with self compiled kernels right from kernel.org. |
|
OK, that sounds like an issue with either bluez or pulseaudio.
Wait a moment. I have a W17 image with me, and the version of bluez is '5.62-2+kali1'. And right now in Kali rolling the version of bluez is still '5.62-2+kali1'. So upgrading your weekly image 2022-W18 will NOT change the version of the bluez package. Or am I missing something? It's the same with pulseaudio, same version in Kali W17 as it's currently in Kali rolling... You should save the list of the packages that get updated, otherwise it's all very confusing. It seems that pipewire went from 0.3.50 to 0.3.51 though, so maybe that's the package that breaks the sound for you. Maybe you can try to downgrade this package. |
|
Yes I found it too. I've installed the new 2022.2 and bluetooth audio devices work. Next thing I try is to install, then upgrade and have a look at configuration files if they differ. Maybe here could be helpful comparing a working life system with an installed and upgraded one. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2022-05-21 05:35 | neyoojhony | New Issue | |
2022-05-21 05:35 | neyoojhony | Issue generated from: 0007699 | |
2022-06-01 07:45 | daniruiz | Assigned To | => daniruiz |
2022-06-01 07:45 | daniruiz | Status | new => closed |
2022-06-01 07:45 | daniruiz | Resolution | open => duplicate |
2022-06-01 07:45 | daniruiz | Relationship added | duplicate of 0007699 |