Bug 364223 - Failure to connect bluetooth headphones
Summary: Failure to connect bluetooth headphones
Status: RESOLVED WORKSFORME
Alias: None
Product: Bluedevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.6.4
Platform: Neon Linux
: NOR grave
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-11 19:00 UTC by Fred
Modified: 2021-01-17 04:33 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred 2016-06-11 19:00:38 UTC
When going through bluetooth "Add device" wizard, select my Bose AE2 SoundLink headphones, which fail to install.



Reproducible: Always

Steps to Reproduce:
0. "Forget device" if listed
1. Turn on Bose AE2 SoundLink headphones 
2. Run "Add Device" wizard
3. select "Bose AE2 SoundLink"

Actual Results:  
Wizard takes a while (~10s) and then says "The setup of Bose AE2 SoundLink has failed"

dmesg says: "Bluetooth: SMP security requested but not available."

bluetoothctl says: "Device [device id] Connected: yes"

From KDE Control Module, device appears as connected, but displays "Type: Unknown"

Audio does not work.

Expected Results:  
From KDE Control Module, device should appear as "Type: Headphones" or "Type: Audio" or something known.

Audio should work.

Don't want to be overly dramatic with the "Grave" severity, but bluetooth audio is unusable for me today after doing a fresh install today... was working with kubuntu 16.04 this morning so possibly an issue for Neon.
Comment 1 David Rosca 2016-06-11 19:16:00 UTC
Similar bug report: https://bugzilla.kernel.org/show_bug.cgi?id=104011

Judging by the error message, this is not issue with Bluedevil but with kernel or BlueZ.
Can you please try to pair with bluetoothctl (You'll need to enable pairing agent with "agent on")?
Comment 2 Fred 2016-06-11 21:50:15 UTC
Thanks for prompt reply.

I do not believe that this is a kernel issue since this was working in kubuntu-16.04 LTS this morning, which as far as I know uses the same kernel version as Neon (currently running 4.4.0-24-generic). I believe bluez should also be the same version...

The reason this *might* be a bug for you is that I would guess that I'm running a later bluedevil version than I was running this morning as I'm now on neon "developer edition" (which I may be the underlying issue here afaik).

I have not been successful using bluetoothctl to connect... here's my current status (device-id redacted):

[bluetooth]# info [device-id redacted]
Device [device-id redacted]
    Name: Bose AE2 SoundLink
    Alias: Bose AE2 SoundLink
    Paired: yes
    Trusted: yes
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID: Bose Corporation (id redacted)
Comment 3 Fred 2016-06-11 21:51:49 UTC
Actually I apologize... I recognize that if I'm having problems with bluetoothctl it's not a bluedevil issue... I'm a little slow sometimes. If you happen to be able to help I would appreciate it! If not, I understand.
Comment 4 Fred 2016-06-11 21:52:29 UTC
Perhaps this is a suitable bug for Neon?
Comment 5 Edmund Kasprzak 2018-02-18 19:44:54 UTC
Fred, do you still have that issue?

I don't have any problems connecting my jabra headphones and xiaomi speaker (both of these are bluetooth of course) on current Neon.

Plasma 5.12.1, KF 5.43.0, Qt 5.9.3.
bluez 5.37, bluedevil 5.12.1
Comment 6 Nate Graham 2020-12-18 19:45:38 UTC
Is it still happening to you?
Comment 7 Bug Janitor Service 2021-01-02 04:34:06 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2021-01-17 04:33:19 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!