Hide Forgot
Description of problem: when i connect my jabra wave+ bluetooth headset, i am not getting the input device for the mic listed in the sound settings. the output for audio work great. there is just no input device to capture audio through the mic. this was working in f19 but stopped working in f20. Version-Release number of selected component (if applicable): bluez-5.12-1.fc20.x86_64 How reproducible: pairing and connecting the headset. Steps to Reproduce: 1. 2. 3. Actual results: no input device for volume control and no input sound captured. Expected results: input device to control mic volume and sound input. Additional info: i captured all output to /var/log/messages from the time i powered on the headset to the time i connected and powered off the headset: --- Dec 17 12:22:07 algeria dbus-daemon: dbus[734]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Dec 17 12:22:07 algeria dbus[734]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Dec 17 12:22:07 algeria systemd: Starting PackageKit Daemon... Dec 17 12:22:07 algeria dbus-daemon: dbus[734]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 17 12:22:07 algeria dbus[734]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 17 12:22:07 algeria systemd: Started PackageKit Daemon. Dec 17 12:22:18 algeria systemd: Reached target Bluetooth. Dec 17 12:22:18 algeria bluetoothd[1005]: /org/bluez/hci0/dev_50_C9_71_95_A4_D8/fd2: fd(30) ready Dec 17 12:22:18 algeria rtkit-daemon[706]: Successfully made thread 9702 of process 2027 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5. Dec 17 12:22:35 algeria dbus-daemon: dbus[734]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.68" (uid=1000 pid=2027 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.14" (uid=0 pid=1005 comm="/usr/libexec/bluetooth/bluetoothd ") Dec 17 12:22:35 algeria dbus[734]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.68" (uid=1000 pid=2027 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.14" (uid=0 pid=1005 comm="/usr/libexec/bluetooth/bluetoothd ") ---
Exact same experience with a plantronics PLT legend headset. Let me know what diagnostics I should run to help track this down. bluez-5.18-1.fc20.x86_64
Having the same issue on Fedora 21 with a Plantronics PLT Legend over bluetooth with: $ rpm -q bluez bluez-5.23-1.fc21.x86_64 Also added a sosreport into this bz in the event that great logs are needed here. I've also validated this with two other associates seeing the same issue.
Created attachment 970155 [details] sosreport for bwalker
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.