Bug 475959 - Provide more human friendly message when device connection fails with no message
Summary: Provide more human friendly message when device connection fails with no message
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Bluetooth in general (other bugs)
Version First Reported In: 6.2.4
Platform: Other Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: David Rosca
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2023-10-22 10:03 UTC by Philippe ROUBACH
Modified: 2025-08-13 18:15 UTC (History)
4 users (show)

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


Attachments
message with the mac address (2.63 MB, image/png)
2023-10-24 08:07 UTC, Philippe ROUBACH
Details
bt connect log (38.31 KB, text/plain)
2025-08-13 07:48 UTC, Philippe ROUBACH
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2023-10-22 10:03:27 UTC
SUMMARY
if i try to manually connect my p PC to the smartphone, this fails.


STEPS TO REPRODUCE
1. click on the bluetooth icon
2. click on "connect"
3. 

OBSERVED RESULT

After a long delay i get a message saying nothing. only the bluetooth address is displayed

EXPECTED RESULT

the PC is connected for "audio" and "telephone"

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

A very interesting experiment :

first step

I try to connect the PC to the Bluetooth network of the phone (PAN) via networkmanager plasmoid.
Result : failure because the Pan is not enabled at the phone

second step

I try to connect to the Bluetooth "telephone" and "audio" protocol via bluedevil plasmoid
result : success !

If we don't do the first step, the second step fails.

Is there something missing in the bluedevil dialog for connecting to the "telephone" and "audio" protocol ?
Comment 1 Philippe ROUBACH 2023-10-22 10:07:11 UTC
I forgot

Operating System: openSUSE Tumbleweed 20231020
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.5.6-1-default (64-bit)
KDE Gears 23.08.2
Comment 2 Nate Graham 2023-10-23 21:05:06 UTC
Can you attach a screenshot of the message saying nothing?
Comment 3 Philippe ROUBACH 2023-10-24 08:07:56 UTC
Created attachment 162534 [details]
message with the mac address

Message saying noting
Comment 4 Nate Graham 2023-10-24 18:50:04 UTC
Thanks for the info.
Comment 5 Nate Graham 2025-04-23 08:14:06 UTC
Sorry we were not able to get to this bug report yet! Can I ask you if the issue is still happening in Plasma 6.3.4 or newer? Thanks a lot!
Comment 6 Philippe ROUBACH 2025-04-23 08:23:57 UTC
(In reply to Nate Graham from comment #5)
> Sorry we were not able to get to this bug report yet! Can I ask you if the
> issue is still happening in Plasma 6.3.4 or newer? Thanks a lot!

Problem still there

Samsung A34, Android 14 'When i sent this report I got a Samsung S7, Android 8)

Operating System: openSUSE Tumbleweed 20250420
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × 12th Gen Intel® Core™ i3-12100
Memory: 15.3 Gio of RAM
Graphics Processor 1: Intel® UHD Graphics 730
Graphics Processor 2: llvmpipe
Manufacturer: ASRock
Product Name: B760M-HDV/M.2 D4
Comment 7 TraceyC 2025-08-12 22:19:58 UTC
Can you try pairing your device through command line with bluetoothctl? This will let us know if there's an underlying system problem.

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. Thanks.
Comment 8 Philippe ROUBACH 2025-08-13 07:48:09 UTC
Created attachment 184029 [details]
bt connect log

I try to connect to "Pschitt" 9C:73:B1:45:FC:B2
Comment 9 Philippe ROUBACH 2025-08-13 07:49:00 UTC
Operating System: openSUSE Tumbleweed 20250811
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.15.8-1-default (64-bit)
Graphics Platform: X11
Comment 10 TraceyC 2025-08-13 16:35:15 UTC
Thanks for the logs, those are helpful. It looks like you tried to connect to the smartphone, and nothing happened, so you tried a second time and got the error that an attempt was already in progress.

I also see a lot of chatter from the bluetooth controller on your system, which appears to be producing an unusual amount of change events. 
This looks like a problem in the bluetooth stack, that Plasma isn't responsible for. Typically this is an issue with the device definition that gets parsed by upstream code; please report to https://github.com/bluez/bluez/issues. Thanks!

Also, the problem with the notification that says nothing other than the phone's identifier is all that bluetoothctl is providing to Plasma, so that's all that's in the message. Something actionable for KDE would be to provide a more useful message when the bluetooth connect event produces no information, along the lines of 
"Failed to connect to <device name and ID>. The bluetooth system failed to provide a reason". I'm sure the developers can come up with something useful here.