Bug 483485

Summary: Bluetooth pairing via GUI fails/Freezes on some devices
Product: [Plasma] plasmashell Reporter: julino.development
Component: Bluetooth in generalAssignee: David Rosca <nowrep>
Status: RESOLVED DOWNSTREAM    
Severity: minor CC: george, kdedev, plasma-bugs-null
Priority: NOR Keywords: qt6
Version First Reported In: 6.3.2   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=482597
https://bugs.kde.org/show_bug.cgi?id=447725
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description julino.development 2024-03-13 21:10:25 UTC
SUMMARY
Tried to pair any bluetooth device via the tray or via system settings on my Hp Omen 16 (2023) Laptop with  Intel AX211 Wireless card does not work. When clicking on next in the add new device window, the progress bar freezes and afterwards the pairing fails.
This is sometimes by a message 
bluedevil-wizard[4537]: 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."
or
"Authentification cancelled"
Manual Pairing via. bluetoothctl does not work when discovery is enabled. Disabling this makes pairing possible. In the GUI pairing window, discovery is enabled all the timing.

(I do not know if this is a bluedevil issue or should be fixed in a lower layer. But at least it gave me a frustrating experience)
Recommendations:
- Add a possibility to stop discovery (e.g. there is already the scanning indicator. Maybe introduce a button to stop discovery)
- Disable discovery prior to trying to pair with a device



STEPS TO REPRODUCE
1. Probably only with my bt card
2. Open "Add New Device..." via tray or settings gui.
3. Try pairing with arbitrary device

OBSERVED RESULT
Window freezes and pairing just fails.

EXPECTED RESULT
Pairing working when clicking the button. No Freeze. A more meaningful error when something fails...

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon latest release
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
-
Comment 1 julino.development 2024-03-13 21:12:49 UTC
After googeling around a bit this does not to be a isolated fault, but happened to others as well:
Comment 2 TraceyC 2024-12-18 18:36:26 UTC
Can you try pairing your device through command line with bluetoothctl? This will let us know if there's an underlying system problem. Thanks.

Instructions to connect using bluetoothctl:
1. `sudo systemctl restart bluetooth`
2. `bluetoothctl`
3. `scan on`
4. Write down the MAC for the device: `[bluetooth]# [NEW] Device 88:C9:XXXXXX Device-name
5. `connect <MAC>`
6. `quit`

Please reply with your results.
Comment 3 Bug Janitor Service 2025-01-02 03:47:27 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2025-01-17 03:48:05 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 5 george 2025-03-01 17:20:37 UTC
I have this problem as well, when running plasma in Tumbleweed. When I want to use my airpods pro 2s, I boot instead to KaOS, which is also running Plasma, often the same version (tho admittedly I didn't check everytime).

I first noticed this problem on January 2 of this year. I hoped it would go away in the course of events, but since it hasn't ...

The only error that appears in journalctl is this:

Mar 01 11:12:57 localhost.localdomain plasmashell[2021]: 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."

I tried using bluetoothctl, as mentioned in one of the replies to this bug.  The problem remained. Here's the output:

bluetooth]# connect 14:14:7D:C4:40:DA
Attempting to connect to 14:14:7D:C4:40:DA
[AirPods Pro]# [CHG] Device 14:14:7D:C4:40:DA Connected: yes
[AirPods Pro]# Failed to connect: org.bluez.Error.Failed br-connection-unknown
[bluetooth]# [CHG] Device 14:14:7D:C4:40:DA Connected: no
[AirPods Pro]# [CHG] Device 14:14:7D:C4:40:DA Connected: yes
[bluetooth]# [CHG] Device 14:14:7D:C4:40:DA Connected: no

Operating System: openSUSE Tumbleweed 20250227
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 ร— AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 30.7 GB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: Framework
Product Name: Laptop 16 (AMD Ryzen 7040 Series)
System Version: A7

Here's the info for KaOS, where the airpods work:

Operating System: KaOS (2025) 
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.12.11-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 ร— AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 30.7 GB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: Framework
Product Name: Laptop 16 (AMD Ryzen 7040 Series)
System Version: A7

Please let me know if anything other info is needed.
Comment 6 TraceyC 2025-03-03 19:13:45 UTC
(In reply to george from comment #5)
> I have this problem as well, when running plasma in Tumbleweed. When I want
> to use my airpods pro 2s, I boot instead to KaOS, which is also running
> Plasma, often the same version (tho admittedly I didn't check everytime).

I'm sorry you're also having trouble pairing your Airpods. Thanks for including the output of bluetoothctl. That indicates the problem lies within bluetoothctl itself, which unfortunately, Plasma has no control over.

I recommend you report the bug to OpenSuse so they can take a look at their packaging of the bluetooth stack. Thanks.
https://en.opensuse.org/openSUSE:Submitting_bug_reports
Comment 7 george 2025-03-03 21:38:37 UTC
OK, thanks! I've submitted the bug to OpenSUSE.