From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218680] New: bluetooth connected status not shown in KDE desktop GUIs
Date: Thu, 04 Apr 2024 07:02:08 +0000 [thread overview]
Message-ID: <bug-218680-62941@https.bugzilla.kernel.org/> (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: linux-bluetooth@vger.kernel.org
Reporter: wolf.seifert@web.de
CC: luiz.dentz@gmail.com
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 <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>
...
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-04-04 7:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 7:02 bugzilla-daemon [this message]
2024-04-04 11:26 ` [Bug 218680] bluetooth connected status not shown in KDE desktop GUIs bugzilla-daemon
2024-04-05 8:30 ` bugzilla-daemon
2024-04-05 8:58 ` bugzilla-daemon
2024-04-05 10:44 ` bugzilla-daemon
2024-04-07 12:12 ` bugzilla-daemon
2024-04-07 12:12 ` bugzilla-daemon
2024-04-10 17:08 ` bugzilla-daemon
2024-04-10 18:59 ` bugzilla-daemon
2024-04-14 4:36 ` bugzilla-daemon
2024-04-17 12:35 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218680-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox