Created attachment 2054958 [details]
bluetoothd debug log

bluetoothd.service overrode for debug information

[Service]
ExecStart=
ExecStart=/usr/libexec/bluetooth/bluetoothd -d

This was fixed in kernel kernel-6.11.4-301.fc41 so rebase to a commit that has at least that kernel. That kernel was also part of F-41 GA so it should be fine there too.

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

Thanks. I should've checked for bugs filed against Rawhide as well.

(In reply to Peter Robinson from comment #2)
> This was fixed in kernel kernel-6.11.4-301.fc41 so rebase to a commit that
> has at least that kernel. That kernel was also part of F-41 GA so it should
> be fine there too.
> 
> *** This bug has been marked as a duplicate of bug 2319597 ***

I've rebased to Fedora 41 and still have the same issue. This should be a different bug.

I'm currently running on this kernel:
Linux 6.11.5-300.fc41.x86_64

Created attachment 2055857 [details]
bluetoothd debug log F41

New log file under Fedora 41. Looks nearly identical, actually.

It's probably bug 2321690, please put details there and answer the questions asked there.

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

While I can reproduce the issue in https://bugzilla.redhat.com/show_bug.cgi?id=2321690 my issue is different.

In ConEst's issue, they were able to disconnect and reconnect the device after the initial pairing.

I am not able to connect to an already paired device (either through UI or bluetoothctl).

I agree that something else is going on here.  This might be certain devices, because my bluetooth Logitech mouse is working, but it is not happy with connecting to my speaker, which was working before F41 upgrade.

Running 6.11.7-300.fc41.x86_64

The problem device is A4:77:33:BF:2F:32 and I think the relevant part of the logs are:

---
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: [signal] org.freedesktop.DBus.Properties.PropertiesChanged
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: src/adapter.c:resume_discovery()
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: src/device.c:device_bonding_failed() status 14
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: src/device.c:device_bonding_complete() bonding (nil) status 0x0e
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr A4:77:33:BF:2F:32 type 0 status 0xe
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: plugins/policy.c:disconnect_cb() reason 3
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: src/adapter.c:adapter_remove_connection()
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: src/adapter.c:dev_disconnected() Device A4:77:33:BF:2F:32 disconnected, reason 3
Nov 14 13:49:30 rhlaptop bluetoothd[8037]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000c
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:avdtp_free() 0x5611b7ea9ed0
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:avdtp_unref() 0x5611b7ea9ed0: ref=0
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/a2dp.c:channel_remove() chan 0x5611b7e74d20
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/sink.c:sink_set_state() State changed /org/bluez/hci0/dev_A4_77_33_BF_2F_32: SINK_STATE_CONNECTING -> SINK_STATE_DISCONNECTED
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:avdtp_unref() 0x5611b7ea9ed0: ref=1
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/a2dp.c:setup_free() 0x5611b7e70d10
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/a2dp.c:setup_unref() 0x5611b7e70d10: ref=0
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: [:1.94:error] < org.bluez.Error.Failed [#591]
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: src/device.c:device_profile_connected() returning response to :1.94
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: src/device.c:device_profile_connected() a2dp-sink Connection refused (111)
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: src/service.c:change_state() 0x5611b7e41880: device A4:77:33:BF:2F:32 profile a2dp-sink state changed: connecting -> disconnected (-111)
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:avdtp_unref() 0x5611b7ea9ed0: ref=2
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/a2dp.c:discover_cb() version 0x0000 err 0x7ffe1f3f89f0
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:connection_lost() Disconnected from A4:77:33:BF:2F:32
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:avdtp_ref() 0x5611b7ea9ed0: ref=3
Nov 14 13:49:11 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to A4:77:33:BF:2F:32: Connection refused (111)
Nov 14 13:48:30 rhlaptop bluetoothd[8037]: [signal] org.freedesktop.DBus.Properties.PropertiesChanged
Nov 14 13:48:30 rhlaptop bluetoothd[8037]: src/adapter.c:connected_callback() hci0 device A4:77:33:BF:2F:32 connected eir_len 0
Nov 14 13:48:30 rhlaptop bluetoothd[8037]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x000b
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: src/service.c:change_state() 0x5611b7e41880: device A4:77:33:BF:2F:32 profile a2dp-sink state changed: disconnected -> connecting (0)
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: profiles/audio/sink.c:sink_connect() stream creation in progress
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: profiles/audio/sink.c:sink_set_state() State changed /org/bluez/hci0/dev_A4_77_33_BF_2F_32: SINK_STATE_DISCONNECTED -> SINK_STATE_CONNECTING
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: profiles/audio/a2dp.c:setup_ref() 0x5611b7e70d10: ref=1
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:avdtp_ref() 0x5611b7ea9ed0: ref=2
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: profiles/audio/avdtp.c:avdtp_ref() 0x5611b7ea9ed0: ref=1
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: profiles/audio/a2dp.c:a2dp_sink_connect() path /org/bluez/hci0/dev_A4_77_33_BF_2F_32
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: src/device.c:connect_profiles() /org/bluez/hci0/dev_A4_77_33_BF_2F_32 (all), client :1.94
Nov 14 13:48:29 rhlaptop bluetoothd[8037]: [:1.94:method_call] > org.bluez.Device1.Connect [#591]
---

This looks very similar to the other results here.

Device is

---
Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
...
[   14.271102] iwlwifi 0000:00:14.3: loaded firmware version 77.0b4c06ad.0 QuZ-a0-hr-b0-77.ucode op_mode iwlmvm
---

It is ... sort of connected?  If I forget it on both the laptop and speaker side (it's a google home speaker, and i can see in the app what it's paired with) and then go through the process, it ends up showing as connected in the google app and shows up as "disconnected" in gnome, but never actually "connects", or at least doesn't stay that way ...

(In reply to Ian Wienand from comment #8)
> I agree that something else is going on here.  This might be certain
> devices, because my bluetooth Logitech mouse is working, but it is not happy
> with connecting to my speaker, which was working before F41 upgrade.

Oh i also found another pair of bluetooth headphones, and they connect and work too.

I wonder if this helps any; this is me trying to connect it via bluetoothctl

---
[MX Master 3]# connect A4:77:33:BF:2F:32
Attempting to connect to A4:77:33:BF:2F:32
[MX Master 3]# hci0 A4:77:33:BF:2F:32 type BR/EDR connected eir_len 0
[MX Master 3]# [CHG] Device A4:77:33:BF:2F:32 Connected: yes
[MX Master 3]# info A4:77:33:BF:2F:32
Device A4:77:33:BF:2F:32 (public)
	Name: Office speaker
	Alias: Office speaker
	Class: 0x00240400 (2360320)
	Icon: audio-card
	Paired: yes
	Bonded: yes
	Trusted: no
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	Modalias: bluetooth:v000Fp1200d1436
[MX Master 3]# Failed to connect: org.bluez.Error.Failed br-connection-refused
[MX Master 3]# hci0 A4:77:33:BF:2F:32 type BR/EDR disconnected with reason 3
[MX Master 3]# [CHG] Device A4:77:33:BF:2F:32 Connected: no
---

Is the device that is not connecting an audio device? Please include the make/model of the device that isn't connecting.

Just like 2321690 I can FORGET the device, then connect to it through `bluetoothctl connect` although strangely `bluetoothctl pair` does not work. But unlike that issue, subsequent connects do not work. I've reconnected the device this way to get info.

My device is a Google Home Mini (now called Nest mini). I'm not sure what the model is, but it looks like it has a broadcom chip.

$ journalctl -k -f
Nov 15 09:24:19 navi kernel: input: Nemini (AVRCP) as /devices/virtual/input/input127

$ udevadm info -p /sys/devices/virtual/input/input127
P: /devices/virtual/input/input127
M: input127
R: 127
U: input
E: DEVPATH=/devices/virtual/input/input127
E: SUBSYSTEM=input
E: PRODUCT=5/f/1200/1436
E: NAME="Nemini (AVRCP)"
E: PHYS="c0:b6:f9:fb:a8:c8"
E: PROP=0
E: EV=100007
E: KEY=2fc800 145200000000 0 10300 49e800000c00 e16800000000f f810000010000ffc
E: REL=0
E: MODALIAS=input:b0005v000Fp1200e1436-e0,1,2,14,k71,72,73,8A,8B,A3,A5,A6,A7,A8,AB,AE,C8,C9,D0,161,164,166,16A,16C,18B,18E,18F,190,191,192,193,195,ramlsfw
E: USEC_INITIALIZED=222627520441
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_BUS=bluetooth

$ cd /usr/lib/udev/hwdb.d
$ grep -zPro '\n[^\n]+v000F[^\n]*\n[^\n]*'

20-bluetooth-vendor-product.hwdb:
bluetooth:v000F*
 ID_VENDOR_FROM_DATABASE=Broadcom Corporation⏎

Also info from bluetoothctl

[Nemini]# info D4:F5:47:0C:FB:04
Device D4:F5:47:0C:FB:04 (public)
        Name: Nemini
        Alias: Nemini
        Class: 0x00240400 (2360320)
        Icon: audio-card
        Paired: yes
        Bonded: yes
        Trusted: no
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Google                    (0000fea0-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v000Fp1200d1436

> Is the device that is not connecting an audio device? Please include the make/model of the device that isn't connecting.

> My device is a Google Home Mini (now called Nest mini).

Mine is also a Google Home Smart Speaker (full size I guess).  per comment https://bugzilla.redhat.com/show_bug.cgi?id=2323328#c9 looks like very similar uuid's ...

I tried 6.11.8 which updated on fedora, but no luck.  

I then installed the recently released 6.12.0-464 from the fedora kernel vanilla repo and ... it just worked like it used to.  

While I haven't bisected, looking through the logs https://bugzilla.kernel.org/show_bug.cgi?id=219458 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7967dc8f797f454d4f4acec15c7df0cdf4801617) seems very much like this issue of sort-of-but-not-really-connecting devices ...

So I believe this has been fixed with the kernel-6.11.10-300.fc41 update, the fedora-release-41-28 release may also aide in improving the situations for AVRCP headsets (Which I think the Sony one is).

That was just promoted to stable today. I updated and tested it.
Confirmed, it did fix my issue!