This is a new problem in Fedora 19: 1. Open sound settings. 2. Power on a bluetooth headset that's paired with your computer, that supports both A2DP and HSP/HFP profiles. 3. Wait for it to show up in the Output tab of sound settings. 4. Select the headset as your output device in sound settings. 5. If it's configured for HSP/HFP, then switch to A2DP, or vice versa. 6. Switch to the input tab and observe how there are now two "Bluetooth Telephony (HSP/HFP)" devices listed. D'oh! I've seen a similar issue where two "Bluetooth Output" devices show up in the Output tab before I do anything at all to the settings. I think this might only happen when the device starts out configured for A2DP. If you keep clicking back and forth between the Output and Input tabs and selecting various ones of the many listed bluetooth devices, more will be added and/or the sound settings app will crash. It's a mess.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
I am unable to reproduce this issue in Fedora 21.
Alas, I was wrong. I just reproduced it in Fedora 21 and managed to get like 6 duplicate devices listed for my bluetooth headset in the Output tab of the sound settings.
Might have something to do with hitting the pause button on my bluetooth headset, rather than just with switching between different bluetooth profiles for the headset, though the latter seems to exacerbate it.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.