Bug 2272864 - bluetoothd error: Authorization request for non-connected device!?
Summary: bluetoothd error: Authorization request for non-connected device!?
Keywords:
Status: CLOSED DUPLICATE of bug 2274047
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 39
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-03 02:51 UTC by Takehiko Abe
Modified: 2024-04-11 02:28 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-11 02:28:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 218680 0 P3 NEW bluetooth connected status not shown in KDE desktop GUIs 2024-04-04 11:27:48 UTC

Description Takehiko Abe 2024-04-03 02:51:31 UTC
1. Please describe the problem:

With kernel-6.7.11-200.fc39.x86_64, I get the bluetoothd error "Authorization request for non-connected device!?" when I try to connect my bluetooth headphone. Sound output to the headphone works fine. But the bluetooth part of Gnome does not seem to recognize the device and the panel indicates it is not connected.

The same error is reported for kernel 6.8.2 at the Arch forum.
https://bbs.archlinux.org/viewtopic.php?id=294310


2. What is the Version-Release number of the kernel:

kernel-6.7.11-200.fc39.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear? 

It first appeared with kernel 6.7.11.

4.
5.
6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Apr 03 11:25:38 localhost bluetoothd[853]: Authorization request for non-connected device!?
Apr 03 11:25:38 localhost wireplumber[2103]: RFCOMM receive command but modem not available: AT+BTRH?
Apr 03 11:25:38 localhost bluetoothd[853]: Authorization request for non-connected device!?
Apr 03 11:25:38 localhost wireplumber[2103]: RFCOMM receive command but modem not available: AT+CSRSF=0,0,0,1,0,0,0
Apr 03 11:25:39 localhost gsd-media-keys[2347]: Unable to get default sink
Apr 03 11:25:40 localhost bluetoothd[853]: Authorization request for non-connected device!?
Apr 03 11:25:40 localhost kernel: input: HD 250BT (AVRCP) as /devices/virtual/input/input19
Apr 03 11:25:40 localhost systemd-logind[867]: Watching system buttons on /dev/input/event10 (HD 250BT (AVRCP))

Reproducible: Always

Comment 1 Takehiko Abe 2024-04-04 06:48:31 UTC
Done git-bisect. The first bad commit is ecd265f2aa01b9da6831a01b1f8bd6c1c3cfb5b9.

#+begin_quote
ecd265f2aa01b9da6831a01b1f8bd6c1c3cfb5b9
Author:     Luiz Augusto von Dentz <luiz.von.dentz>
AuthorDate: Wed Jan 31 11:24:19 2024 -0500
Commit:     Sasha Levin <sashal>
CommitDate: Tue Mar 26 18:18:23 2024 -0400

Parent:     9dd082b4feb6 Bluetooth: Remove BT_HS
Merged:     (no branch, bisect started on 6fc5460ed8dd)
Contained:  6-7.y
Follows:    v6.7.10 (343)
Precedes:   v6.7.11 (364)

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>
Signed-off-by: Sasha Levin <sashal>

2 files changed, 18 insertions(+), 7 deletions(-)
net/bluetooth/hci_event.c | 21 ++++++++++++++-------
net/bluetooth/mgmt.c      |  4 ++++

#+end_quote

Comment 2 Takehiko Abe 2024-04-05 11:19:40 UTC
The patch is available:

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

It works.

Comment 3 Takehiko Abe 2024-04-11 02:28:14 UTC

*** This bug has been marked as a duplicate of bug 2274047 ***


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