Bug 16276 - A problem in establishing a connection with the Bluetooth audio device
Summary: A problem in establishing a connection with the Bluetooth audio device
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 5
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDHELP, NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-07-03 02:01 CEST by Rod Goslin
Modified: 2017-07-03 01:54 CEST (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Rod Goslin 2015-07-03 02:01:47 CEST
Description of problem: I've lately thought to enable audio output through Bluetooth, on a Mageia 5 desktop installation To this end I fitted a Bluetooth USB adaptor, to pair with  a set of Plantronic earphones (Plantronic BB.FIT). Having problems with the installed Bluetooth manager, The forum suggested I use Blueman. This was better, in presenting more detail of what was going on. I was able to see the adaptor, in Blueman and to set it to pair with the headset. However, I was unable to obtain a stable connection with the headset in pairing mode. Blueman would indicate a connection, but in anything from less than a second, to about twenty seconds the connection would fail. I bought more Bluetooth adaptors from different suppliers (five in all). I also had a second headset, a Plantronics BB903+. With all the adaptors and both headsets in combination the same problem prevailed. I also have mageia 5 installed on an Asus netbook and a Lenovo thinkpad. Repeating all combinations on these two machines also failed in the same fashion. I also tried bluetoothctl, with identical results, but in slightly more detail. That the pairing was successful, was indicated by swithching off the headset and switching it back on again, the adaptor/headset pair would attempt a connection, which would then fail.. On  (very) few occasions on the laptop, a stable connection would be obtained and sound enabled in the headset, but these occasions were very, very few and were neither predictable nor explainable. The headset (both) work fine on an Android phone, and a limited test in MS Windows also obtained a stable connection


Version-Release number of selected component (if applicable): Mageia 5


How reproducible: Reproducible in virtually every occasion


Steps to Reproduce:
1.Plug in adaptor
2.Set headset in pairing mode
3.Open Blueman (or bluetoothctl)
4 carry out a search for device (headset)
5 set pairing, and set trust (optional)
6 observe connection, and subsequent dis-connection
7 turn on/off headset to demonstrate re-connection failure
If already paired, steps steps 2-5 are not required

Reproducible: 

Steps to Reproduce:
Filip Komar 2015-07-03 07:05:11 CEST

CC: atelier-bugs, sysadmin-bugs => filip.komar
Component: Bugzilla => RPM Packages
Version: unspecified => 5
Assignee: sysadmin-bugs => bugsquad
Product: Infrastructure => Mageia
Target Milestone: --- => Mageia 5
Summary: A problen in establishinf a connection in Bluetooth audio device => A problem in establishing a connection with the Bluetooth audio device

Filip Komar 2015-07-03 07:05:32 CEST

CC: filip.komar => (none)

Florian Hubold 2015-07-03 18:39:36 CEST

CC: (none) => doktor5000

Comment 1 Rod Goslin 2015-07-05 22:07:59 CEST
As a follow up to my earlier post, I've now tried the operation with another desktop PC with Mga5 as the OS, with the same results as before. To (hopefully) eliminate any possibility that the devices (all Plantronics) are the source of the problem, I bought  to clarify the picture.a bluetooth speaker by an entirely different manufacturer. Alas, the results are just the same as before. I also tried the speaker with an Android tablet and it works fine.. I hope this helps
Comment 2 Rod Goslin 2015-07-05 22:12:23 CEST
OOps, A typo there. The "to clarify the issue" should have come at the end of the entry.
Comment 3 Marja Van Waes 2015-07-06 17:27:06 CEST
The forums thread is here:

https://forums.mageia.org/en/viewtopic.php?f=26&t=9865

CC'ing Colin, who might have an idea.

CC: (none) => mageia, marja11

Comment 4 Samuel Verschelde 2016-11-01 13:33:29 CET
Sorry for taking so long for triaging your bug report. It's not an easy one, since we don't know where the problem comes from, and our pulseaudio "expert" is very busy at the moment.

Adding more packagers in CC in case someone can help debugging this.

Also, would you have the possibility to test in a recent cauldron install (preferrably via net-install to have the latest)?

Keywords: (none) => NEEDHELP
CC: (none) => pkg-bugs

Comment 5 Marja Van Waes 2017-03-01 08:45:55 CET
Why did we never give a link to this page
https://wiki.mageia.org/en/Support:DebuggingSoundProblems

Because the page doesn't mention anything about debugging bluetooth problems?

CC'ing kernel & drivers maintainers, in case they can give a good link about how to do that.

Btw, Rod, is this bug still valid?

Keywords: (none) => NEEDINFO
CC: (none) => kernel

Comment 6 Marja Van Waes 2017-03-12 09:34:25 CET
(In reply to Marja van Waes from comment #5)

> 
> Btw, Rod, is this bug still valid?

Is it?
Comment 7 Marja Van Waes 2017-07-02 22:44:02 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, _please_ reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 8 Rod Goslin 2017-07-03 01:54:45 CEST
My apologies, Marja. I had thought that I had replied to your earlier post, but it would seem not to have got into the system. I did try the problem again, with the same result. If I install Mga6, I'll check the situation again, and if necessary, post another bug report.

Regards, Rod

Note You need to log in before you can comment on or make changes to this bug.