You are not logged in.
Can anyone confirm that linux 6.8.3.arch1-1 solves the issue?
The commit that fixed the bluetooth bug in linux 6.8.3: https://github.com/archlinux/linux/comm … 0e1725d1d2
Offline
I now addressed the original cause of this thread at kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=218680
Offline
Can anyone confirm that linux 6.8.3.arch1-1 solves the issue?
No. KDE6 Bluetooth systray still says connect with available battery. This happens only when headset connects to pc, not another way around.
Apr 04 17:12:01 masa-pc bluetoothd[896]: Authorization request for non-connected device!?
Offline
KDE6 Bluetooth systray still says connect with available battery. This happens only when headset connects to pc, not another way around.
Was the issue inroduced by 6.8.2.arch1-1? Is it caused by 81526f2920bf8a03b670dbc2d45f35f204344d55 (as in https://bbs.archlinux.org/viewtopic.php … 1#p2162161)?
Offline
Masardius wrote:KDE6 Bluetooth systray still says connect with available battery. This happens only when headset connects to pc, not another way around.
Was the issue inroduced by 6.8.2.arch1-1? Is it caused by 81526f2920bf8a03b670dbc2d45f35f204344d55 (as in https://bbs.archlinux.org/viewtopic.php … 1#p2162161)?
Yes, I'm using 6.8.1 currently. Is the fix in 6.8.3? I still get same behavior.
Last edited by Masardius (2024-04-04 14:48:29)
Offline
Yes, I'm using 6.8.1 currently. Is the fix in 6.8.3? I still get same behavior.
No. Would it help if I built you 6.8.3 with that commit reverted?
Offline
Masardius wrote:Yes, I'm using 6.8.1 currently. Is the fix in 6.8.3? I still get same behavior.
No. Would it help if I built you 6.8.3 with that commit reverted?
That would be awesome!
Offline
6.8.3.arch1 with 81526f2920bf8a03b670dbc2d45f35f204344d55 reverted and pkgrel incremented to 1.1:
https://drive.google.com/file/d/1SKIx3M … sp=sharing linux-6.8.3.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1S3aO_U … sp=sharing linux-headers-6.8.3.arch1-1.1-x86_64.pkg.tar.zst
Offline
6.8.3.arch1 with 81526f2920bf8a03b670dbc2d45f35f204344d55 reverted and pkgrel incremented to 1.1:
https://drive.google.com/file/d/1SKIx3M … sp=sharing linux-6.8.3.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1S3aO_U … sp=sharing linux-headers-6.8.3.arch1-1.1-x86_64.pkg.tar.zst
It works! Thanks
Offline
Hi,
I'm also have the same problem with 6.6.23-1-lts
Has it been fixed in kernel-lts yet?
Anton
Offline
If you mean by "it" that the "bluetooth connection status is not shown correctly in the GUI anymore", the answer is NO. Neither for 6.8.3.arch1-1 nor 6.6.24-1. I opened a ticket here: https://bugzilla.kernel.org/show_bug.cgi?id=218680. Feel free to push it by adding a comment there.
Offline
What about the OOPS null pointer dereference? Has it been fixed?
Offline
What about the OOPS null pointer dereference? Has it been fixed?
Yes
For "bluetooth connection status is not shown correctly in the GUI anymore" https://bugzilla.kernel.org/show_bug.cgi?id=218680
6.8.4-arch1-1.1 with d6126dfaf91e46ffba41f6bc82e018a5ef521bc7 applied and pkgrel incremented to 1.1:
https://drive.google.com/file/d/1Lsx8UH … sp=sharing linux-6.8.4.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1PaaXQu … sp=sharing linux-headers-6.8.4.arch1-1.1-x86_64.pkg.tar.zst
Last edited by loqs (2024-04-05 12:15:55)
Offline
I also had this connection issue with my AX200 and Kernel 6.8.2. Downgraded to 6.8.1 solved the issue for me.
Now I just installed Kernel 6.8.4 from core-testing and the issue is back. I'm able to connect my Bluetooth headset, but it is shown as not connected in Gnome.
Offline
I also had this connection issue with my AX200 and Kernel 6.8.2. Downgraded to 6.8.1 solved the issue for me.
Now I just installed Kernel 6.8.4 from core-testing and the issue is back. I'm able to connect my Bluetooth headset, but it is shown as not connected in Gnome.
Is it resolved in 6.8.4-arch1-1.1 with d6126dfaf91e46ffba41f6bc82e018a5ef521bc7 applied (see post #63)?
Offline
I've tried linux-6.8.3.arch1-1 and linux-headers-6.8.3.arch1-1, along with the newly posted linux-6.8.4.arch1-1 and linux-headers-6.8.4.arch1-1. I'm still having problems on this end (KDE plasmoid says "Bluetooth is disabled"). If I downgrade to 6.7.9.arch1, for each of those packages, respectively, I get Bluetooth back. I'm not sure where to start, really, but here's my output from
sudo journalctl -b | grep -i bluetooth
Apr 05 13:16:53 ryzenarch kernel: Bluetooth: Core ver 2.22
Apr 05 13:16:53 ryzenarch kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 05 13:16:53 ryzenarch kernel: Bluetooth: HCI device and connection manager initialized
Apr 05 13:16:53 ryzenarch kernel: Bluetooth: HCI socket layer initialized
Apr 05 13:16:53 ryzenarch kernel: Bluetooth: L2CAP socket layer initialized
Apr 05 13:16:53 ryzenarch kernel: Bluetooth: SCO socket layer initialized
Apr 05 13:16:55 ryzenarch systemd[1]: Starting Bluetooth service...
Apr 05 13:16:55 ryzenarch (uetoothd)[1078]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: Bluetooth daemon 5.73
Apr 05 13:16:55 ryzenarch systemd[1]: Started Bluetooth service.
Apr 05 13:16:55 ryzenarch systemd[1]: Reached target Bluetooth Support.
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: Starting SDP server
Apr 05 13:16:55 ryzenarch kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Apr 05 13:16:55 ryzenarch kernel: Bluetooth: BNEP filters: protocol multicast
Apr 05 13:16:55 ryzenarch kernel: Bluetooth: BNEP socket layer initialized
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: src/plugin.c:init_plugin() System does not support bap plugin
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: src/plugin.c:init_plugin() System does not support bass plugin
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: src/plugin.c:init_plugin() System does not support mcp plugin
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: src/plugin.c:init_plugin() System does not support vcp plugin
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: src/plugin.c:init_plugin() System does not support micp plugin
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: src/plugin.c:init_plugin() System does not support ccp plugin
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: src/plugin.c:init_plugin() System does not support csip plugin
Apr 05 13:16:55 ryzenarch bluetoothd[1078]: Bluetooth management interface 1.22 initialized
Apr 05 13:16:55 ryzenarch vmware-usbarbitrator[1084]: USBArb: DevID(380870029): Device 2: name:Intel\ Bluetooth\ Adapter vid:8087 pid:0029 path:1/10/2 speed:full family:wireless,bluetooth arbRuntimeKey:3 version:5 owner:(null).
Apr 05 13:16:55 ryzenarch NetworkManager[1092]: <info> [1712341015.2402] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
Apr 05 13:16:55 ryzenarch kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
Apr 05 13:16:55 ryzenarch kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Apr 05 13:17:09 ryzenarch systemd[1]: Starting Bluetooth management mechanism...
Apr 05 13:17:10 ryzenarch systemd[1]: Started Bluetooth management mechanism.
Apr 05 13:17:43 ryzenarch plasmashell[2247]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/FullRepresentation.qml:65:13: QML Toolbar: Binding loop detected for property "leftInset"
Apologies in advance if this isn't helpful.
Last edited by remanifest (2024-04-05 18:29:36)
Offline
I've tried linux-6.8.3.arch1-1 and linux-headers-6.8.3.arch1-1, along with the newly posted linux-6.8.4.arch1-1 and linux-headers-6.8.4.arch1-1. I'm still having problems on this end (KDE plasmoid says "Bluetooth is disabled"). If I downgrade to 6.7.9.arch1, for each of those packages, respectively, I get Bluetooth back.
linux-6.8.3.arch1-1 and linux-6.8.4.arch1-1 address two issues introduced in 6.8.2.arch1-1. that were not present in 6.8.1.arch1-1. Is your issue present in 6.8.1.arch1-1?
Offline
remanifest wrote:I've tried linux-6.8.3.arch1-1 and linux-headers-6.8.3.arch1-1, along with the newly posted linux-6.8.4.arch1-1 and linux-headers-6.8.4.arch1-1. I'm still having problems on this end (KDE plasmoid says "Bluetooth is disabled"). If I downgrade to 6.7.9.arch1, for each of those packages, respectively, I get Bluetooth back.
linux-6.8.3.arch1-1 and linux-6.8.4.arch1-1 address two issues introduced in 6.8.2.arch1-1. that were not present in 6.8.1.arch1-1. Is your issue present in 6.8.1.arch1-1?
Yes, it's present in 6.8.1-arch1-1 as well. It looks like the problem started with 6.8.0-arch1-1 for me (with 6.7.9.arch1-1 having the expected Bluetooth functionality).
Last edited by remanifest (2024-04-05 18:45:31)
Offline
Yes, it's present in 6.8.1-arch1-1 as well.
I would suggest starting a new thread for your issue. Please include it a full system journal for a boot with and without the issue.
Offline
Is it resolved in 6.8.4-arch1-1.1 with d6126dfaf91e46ffba41f6bc82e018a5ef521bc7 applied (see post #63)?
Yes!! In Kernel 6.8.4-arch1-1.1 the issue is solved!
I installed "linux-6.8.4.arch1-1.1-x86_64.pkg.tar.zst" and now my Bluetooth headset is connected, and it's also shown as connected in Gnome!
What to do to get this fix into the Kernel that will be released??
Offline
What to do to get this fix into the Kernel that will be released??
It will make its way through to a stable kernel. You could open an issue on the Arch gitlab instance against the kernel package asking for the fix to be cherry-picked ahead of upstream back-porting it.
Offline
I don't know how to do that ... I'm just an Arch User ...
Offline
I don't know how to do that ... I'm just an Arch User ...
See the message at the top of https://gitlab.archlinux.org/archlinux for how to get an account on Arch's gitlab. Then follow Bug reporting guidelines. I do not as a general policy open bug reports for issues I do not suffer from and can not reproduce as a would just be acting as the messenger and I do not think that is the most productive use of my limited time.
Offline
I do not as a general policy open bug reports for issues I do not suffer from and can not reproduce as a would just be acting as the messenger and I do not think that is the most productive use of my limited time.
This is and was not what I want you to do! Just wanted to get help how to do it by myself. Thanks for the link!
Offline
Now that "bluetooth connection status is not shown correctly in the GUI anymore" has been fixed upstreams (see https://bugzilla.kernel.org/show_bug.cgi?id=218680 and https://git.kernel.org/pub/scm/linux/ke … a5ef521bc7 ) all we have to do is to wait for the fix to make it into the arch linux kernels.
If you do not want to wait you can either user the kernel made by @loqs (https://drive.google.com/file/d/1Lsx8UH … sp=sharing) or build it yourself locally:
$ git clone https://gitlab.archlinux.org/archlinux/packaging/packages/linux.git
Create a patch file bluetooth.patch with this content:
diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
index cf3b8e9b7b3ba1..b0970462a68996 100644
--- a/net/bluetooth/l2cap_core.c
+++ b/net/bluetooth/l2cap_core.c
@@ -4063,8 +4063,7 @@ static int l2cap_connect_req(struct l2cap_conn *conn,
return -EPROTO;
hci_dev_lock(hdev);
- if (hci_dev_test_flag(hdev, HCI_MGMT) &&
- !test_and_set_bit(HCI_CONN_MGMT_CONNECTED, &hcon->flags))
+ if (hci_dev_test_flag(hdev, HCI_MGMT))
mgmt_device_connected(hdev, hcon, NULL, 0);
hci_dev_unlock(hdev);
Edit PKGBUILD and insert inside of prepare():
patch -p1 < ../../bluetooth.patch
Set the number of processors make shall use:
$ export MAKEFLAGS="-j 4"
Build and install:
$ makepkg -si
I did this successfully for linux and linux-lts.
Offline