Bug 218680 - bluetooth connected status not shown in KDE desktop GUIs
Summary: bluetooth connected status not shown in KDE desktop GUIs
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: Intel Linux
: P3 normal
Assignee: linux-bluetooth@vger.kernel.org
URL: https://github.com/archlinux/linux.git
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-04 07:02 UTC by wolf.seifert
Modified: 2024-04-17 12:35 UTC (History)
4 users (show)

See Also:
Kernel Version: 6.8.2
Subsystem:
Regression: Yes
Bisected commit-id: 81526f2920bf8a03b670dbc2d45f35f204344d55


Attachments

Description wolf.seifert 2024-04-04 07:02:08 UTC
Since 6.8.2 bluetooth connected status is not shown any more in KDE desktop GUIs: it looks disconnected but in fact is connected and working (bluetooth headset).

$ systemctl status bluetooth
bluetoothd[413]: Authorization request for non-connected device!? (in RED)

The "Authorization request for non-connected device!?" also appears in the journalctl output.


It turned out that commit "81526f2920bf8a03b670dbc2d45f35f204344d55" is responsible for this malfunction: I made an Arch Linux package build for 6.8.2.arch1-1 with this single commit "81526f2920bf8a03b670dbc2d45f35f204344d55" reverted and it worked again. So "81526f2920bf8a03b670dbc2d45f35f204344d55" is the one and only cause for this malfunction.


$ git show 81526f2920bf8a03b670dbc2d45f35f204344d55
commit 81526f2920bf8a03b670dbc2d45f35f204344d55
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Wed Jan 31 11:24:19 2024 -0500

    Bluetooth: hci_event: Fix not indicating new connection for BIG Sync
    
    [ Upstream commit eeda1bf97bb500a901f7a9ee5615bad2160f2378 ]
    
    BIG Sync (aka. Broadcast sink) requires to inform that the device is
    connected when a data path is active otherwise userspace could attempt
    to free resources allocated to the device object while scanning.
    
    Fixes: 1d11d70d1f6b ("Bluetooth: ISO: Pass BIG encryption info through QoS")
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
...
Comment 1 Takehiko Abe 2024-04-04 11:26:22 UTC
The same symptom with Gnome. Fedora 39 Kernel 6.7.11. git-bisect points to the same commit for linux-6.7.y: ecd265f2aa01b9da6831a01b1f8bd6c1c3cfb5b9
Comment 2 Bagas Sanjaya 2024-04-05 08:30:46 UTC
Please test the proposed fix [1].

[1]: https://lore.kernel.org/all/20240404185022.1.Ic27505c8f1ca7d4a653b1dcc1b08cdfc862a4622@changeid/
Comment 3 Takehiko Abe 2024-04-05 08:58:16 UTC
(In reply to Bagas Sanjaya from comment #2)

Tested the patch with 6.7.12 stable branch. It works. It fixed the problem.

Thank you.
Comment 4 max 2024-04-10 17:08:40 UTC
Working for me too! Can this patch please be submitted to the stable tree?
Comment 5 Luiz Von Dentz 2024-04-10 18:59:42 UTC
(In reply to max from comment #4)
> Working for me too! Can this patch please be submitted to the stable tree?

Will do that later today.
Comment 6 wolf.seifert 2024-04-14 04:36:57 UTC
I cannot find the fix in linux kernel archives "stable 6.8.6" (2024-04-13) or "longterm 6.6.27" (2024-04-13), only in "next-20240412" (2024-04-12).

Why? When will it be in stable and longterm?
Comment 7 wolf.seifert 2024-04-17 12:35:19 UTC
I found the fix now in linux kernel archives "stable 6.8.7" (2024-04-17) and "longterm 6.6.28" (2024-04-17).

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