Bug 495348 - Failing to pair Google nest mini speaker via bluetooth
Summary: Failing to pair Google nest mini speaker via bluetooth
Status: RESOLVED FIXED
Alias: None
Product: Bluedevil
Classification: Plasma
Component: wizard (show other bugs)
Version: 6.2.3
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-25 15:29 UTC by Masoud
Modified: 2024-12-01 17:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Masoud 2024-10-25 15:29:55 UTC
***
When I try to pair Google nest mini speaker I get the following message in journal:

kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
***

SUMMARY


STEPS TO REPRODUCE
1. Try to pair Google nest mini speaker

OBSERVED RESULT
GUI wizard fails and journal reports the following:
kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

EXPECTED RESULT
The Bluetooth pairing to succeed.

SOFTWARE/OS VERSIONS
OS: Fedora 40
Kernel-Version: 6.11.4
KDE Plasma Version: 6.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
Graphics Platform: Wayland
Comment 1 Nate Graham 2024-11-05 22:14:07 UTC
Is there already another device paired with your Google nest mini speaker, by any chance?
Comment 2 Masoud 2024-11-05 22:19:17 UTC
Hi Nate,

Many thanks for getting back to me.

My phone is paired to my speaker, but I always disconnect it before trying to pair my speaker to my PC. Mind you, this problem has only started happening recently and never existed before.

If it helps at all, I have updated to the following software/os versions now as part of Fedora updates:
SOFTWARE/OS VERSIONS
OS: Fedora 41
Kernel-Version: 6.11.5
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Graphics Platform: Wayland
Comment 3 Nate Graham 2024-11-06 18:40:43 UTC
Thanks! I'll let folks who know more about Bluetooth take over from here.
Comment 4 Masoud 2024-11-08 09:08:43 UTC
Thanks Nate :)
Comment 5 Masoud 2024-11-09 12:49:43 UTC
I'm afraid I'm having the same problem with my XBox Controller. I'm getting br-connection-create-socket error in Bluetooth config screen.
Comment 6 Masoud 2024-11-09 12:52:13 UTC
This is the log from bluetoothctl in regards to my XBox Controller

[bluetooth]# [CHG] Device 5C:BA:37:59:A0:72 Connected: no
[bluetooth]# Failed to pair: org.bluez.Error.AuthenticationCanceled
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 Connected: yes
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 Modalias: usb:v045Ep02FDd0903
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 ServicesResolved: yes
[Xbox Wireless Controller]# Failed to connect: org.bluez.Error.NotAvailable br-connection-profile-unavailable
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 ServicesResolved: no
Comment 7 Masoud 2024-11-09 19:32:11 UTC
I managed to connect my XBox Controller via bluetoothctl. I though this log might be useful for debugging:

[bluetooth]# remove 5C:BA:37:59:A0:72
[bluetooth]# [DEL] Device 5C:BA:37:59:A0:72 Xbox Wireless Controller
[bluetooth]# Device has been removed
[bluetooth]# power  on
[bluetooth]# Changing power on succeeded
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 34:CF:F6:24:D7:9E Discovering: yes
[bluetooth]# [NEW] Device 5C:BA:37:59:A0:72 Xbox Wireless Controller
[bluetooth]# list
Controller 34:CF:F6:24:D7:9E bluedream [default]
[bluetooth]# [CHG] Device 5C:BA:37:59:A0:72 Modalias: usb:v045Ep02E0d0408
[bluetooth]# [CHG] Device 5C:BA:37:59:A0:72 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[bluetooth]# trust 5C:BA:37:59:A0:72
[bluetooth]# [CHG] Device 5C:BA:37:59:A0:72 Trusted: yes
[bluetooth]# Changing 5C:BA:37:59:A0:72 trust succeeded
[bluetooth]# pair [NEW] Device 20:44:41:7C:E0:76 P016 SkyQ LC103
[bluetooth]# pair 5C:BA:37:59:A0:72
Attempting to pair with 5C:BA:37:59:A0:72
[bluetooth]# connect 5C:BA:37:59:A0:72
Attempting to connect to 5C:BA:37:59:A0:72
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 Connected: yes
[Xbox Wireless Controller]# default-agent
[Xbox Wireless Controller]# Default agent request successful
[Xbox Wireless Controller]# connect 5C:BA:37:59:A0:72
Attempting to connect to 5C:BA:37:59:A0:72
[Xbox Wireless Controller]# Failed to connect: org.bluez.Error.InProgress br-connection-busy
[bluetooth]# [CHG] Device 5C:BA:37:59:A0:72 Connected: no
[bluetooth]# Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]# [CHG] Device 5C:BA:37:59:A0:72 WakeAllowed: yes
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 Connected: yes
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 Modalias: usb:v045Ep02FDd0903
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 ServicesResolved: yes
[Xbox Wireless Controller]# [CHG] Device 5C:BA:37:59:A0:72 Paired: yes


Please let me know if you need any details and I'll happily send you whatever logs you need.
Comment 8 Masoud 2024-12-01 17:25:24 UTC
Fixed this by resetting Google nest mini speaker.