Skip to contentSkip to conversation

New: bluetooth connected status not shown in KDE desktop GUIs

Bug 218680 [email protected] 1 participant 11 messages Apr 4, 2024 – Apr 17, 2024 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=218680

               URL: https://github.com/archlinux/linux.git
            Bug ID: 218680
           Summary: bluetooth connected status not shown in KDE desktop
                    GUIs
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.8.2
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
        Regression: Yes
           Bisected 81526f2920bf8a03b670dbc2d45f35f204344d55
         commit-id:

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 <[email protected]>
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")

...

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

[Bug 218680] bluetooth connected status not shown in KDE desktop GUIs

https://bugzilla.kernel.org/show_bug.cgi?id=218680

Takehiko Abe ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Takehiko Abe ([email protected]) ---
The same symptom with Gnome. Fedora 39 Kernel 6.7.11. git-bisect points to the same commit for linux-6.7.y: ecd265f2aa01b9da6831a01b1f8bd6c1c3cfb5b9

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#2 lore raw

[Bug 218680] bluetooth connected status not shown in KDE desktop GUIs

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=218680

Bagas Sanjaya ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #2 from Bagas Sanjaya ([email protected]) --- Please test the proposed fix [1].

[1]:
https://lore.kernel.org/all/20240404185022.1.Ic27505c8f1ca7d4a653b1dcc1b08cdfc862a4622@changeid/

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#3 lore raw

[Bug 218680] bluetooth connected status not shown in KDE desktop GUIs

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=218680

--- Comment #3 from Takehiko Abe ([email protected]) --- (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.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#4 lore raw

[Bug 218680] bluetooth connected status not shown in KDE desktop GUIs

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=218680

Artem S. Tashkinov ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX
Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#7 lore raw

[Bug 218680] bluetooth connected status not shown in KDE desktop GUIs

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=218680

max ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
                   |                            |g

--- Comment #4 from max ([email protected]) --- Working for me too! Can this patch please be submitted to the stable tree?

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#8 lore raw

[Bug 218680] bluetooth connected status not shown in KDE desktop GUIs

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=218680

--- Comment #5 from Luiz Von Dentz ([email protected]) --- (In reply to max from comment #4)

Quoted 1 line

Working for me too! Can this patch please be submitted to the stable tree?

Will do that later today.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#9 lore raw

[Bug 218680] bluetooth connected status not shown in KDE desktop GUIs

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=218680

--- Comment #6 from [email protected] ---
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?

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.