Bug 749911
| Summary: | Bluetooth headset fails to connect after successfully pairing | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Simon Binnie <s.binnie> | ||||||
| Component: | bluez | Assignee: | Bastien Nocera <bnocera> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | bnocera, dwmw2, jaragunde, marcel, s.binnie | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-07 15:28:36 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 530739 [details]
Log output when the device is successfully connected, disconnected and then unsuccessfully reconnected.
Again this is with bluetoothd running in the foreground as /usr/sbin/bluetoothd -n -v
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Created attachment 530738 [details] Successful initial connection when running bluetoothd -d -n Description of problem: I can pair my Samsung H1500 headset and it operates fine until the first time it is disconnected. After that any subsequent attempt to connect the headset fails and produces the lines: Oct 28 22:11:02 syme bluetoothd[2893]: Permission denied (13) Oct 28 22:11:02 syme bluetoothd[2893]: bluetoothd[2893]: Permission denied (13) in /var/log/messages . Version-Release number of selected component (if applicable): bluez.x86_64 4.87-7.fc15 @updates kernel.x86_64 2.6.40.6-0.fc15 @updates How reproducible: Every time. Steps to Reproduce: 1.Pair the headset. 2.Disconnect headset 3.Connect headset Actual results: Connecting the headset fails with log messages: Oct 28 22:11:02 syme bluetoothd[2893]: Permission denied (13) Oct 28 22:11:02 syme bluetoothd[2893]: bluetoothd[2893]: Permission denied (13) Expected results: Headset should be connected and showing as an audio device in Sound Settings. Additional info: I experimented running /usr/sbin/bluetoothd directly in the foreground with verbose logging turned on. With this you can connect the headset once, but any subsequent attempts to disconnect and reconnect fail until bluetoothd is killed and restarted (again in the foreground). The two attachments show the output from the initial successful connection, and the subsequent failed connection respectively.