https://bugs.kde.org/show_bug.cgi?id=526761
Bug ID: 526761
Summary: The bluedevil applet and its pairing assistant don't
show any information on why a connection has failed
Classification: Plasma
Product: plasmashell
Version First master
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Bluetooth in general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
Created attachment 196904
--> https://bugs.kde.org/attachment.cgi?id=196904&action=edit
No information
DESCRIPTION
The bluedevil connection assistant does not show any useful information on why
a connection to an audio device failed.
It just prints something along the lines of "Failed to connect to device" with
zero information on what went wrong to be able to fix the problem, which is
quite frustrating.
With only that phrase I had to dig through bluetoothctl and the journal to get
an idea of what went wrong in my specific case:
--- bluez
[CHG] Device B4:76:4A:ED:51:E3 Connected: yes
[SIGNAL] BREDR.Disconnected - org.bluez.Reason.Local, Connection terminated by
local host
[SIGNAL] Disconnected - org.bluez.Reason.Local, Connection terminated by local
host
[CHG] Device B4:76:4A:ED:51:E3 Connected: no
--- then journal
oct 06 21:37:37 moonvampire systemd[1]: Started Bluetooth service.
oct 06 21:37:37 moonvampire bluetoothd[85195]: Starting SDP server
oct 06 21:37:37 moonvampire bluetoothd[85195]: Bluetooth management interface
1.23 initialized
oct 06 21:37:37 moonvampire bluetoothd[85195]: Battery Provider Manager created
oct 06 21:37:40 moonvampire bluetoothd[85195]:
src/service.c:btd_service_connect() a2dp-sink profile connect failed for
B4:76:4A:ED:51:E3: Protocol not available
oct 06 21:37:41 moonvampire bluetoothd[85195]:
src/service.c:btd_service_connect() a2dp-sink profile connect failed for
B4:76:4A:ED:51:E3: Protocol not available
oct 06 21:37:41 moonvampire bluetoothd[85195]:
src/service.c:btd_service_connect() a2dp-sink profile connect failed for
B4:76:4A:ED:51:E3: Protocol not available
oct 06 21:37:41 moonvampire bluetoothd[85195]:
src/service.c:btd_service_connect() a2dp-sink profile connect failed for
B4:76:4A:ED:51:E3: Protocol not available
oct 06 21:39:02 moonvampire bluetoothd[85195]:
src/service.c:btd_service_connect() a2dp-sink profile connect failed for
B4:76:4A:ED:51:E3: Protocol not available
oct 06 21:39:02 moonvampire bluetoothd[85195]:
src/service.c:btd_service_connect() a2dp-sink profile connect failed for
B4:76:4A:ED:51:E3: Protocol not available
---
only after having digged through the system logs there was information about
the actual problem, not in the user friendly assistant.
STEPS TO REPRODUCE
Note that in my specific case I use real pulseaudio because of a (yet) unfixed
issue on Pipewire/wireplumber stack, in Arch Linux.
1. Install bluez5 but do not install bluez-libs, sbc and pulseaudio-bluetooth.
2. Try to connect to an audio device.
OBSERVED RESULT
A "the connection failed" banner with no information about the error
EXPECTED RESULT
IF the connection fails, information about what actually went wrong, which is
very available, should be present in the error message pretty much like how k3b
warns about missing libraries itself.
SOFTWARE/OS VERSIONS
Distribution: Arch Linux
KDE Plasma version: 6.7.5
KDE Frameworks version: 6.30.0
Qt version: 6.11.2
--
You are receiving this mail because:
You are watching all bug changes.
