Description of problem: In bluez-util ver. 3.x has the pairing process changed and the old way with pinhelper is not working any more. The new way is a component that is called passkey-agent, but the make script just compile it but doesnt install it. To fill the gap/need of a way to pair bluetooth devices from the cli or via a daemon I would like to suggest that the passkey-agent and a start stop script ++ is incorporated into either the bluez-util rpm or a bluez-util-pin package. Version-Release number of selected component (if applicable): bluez-util ver. 3.x How reproducible: Make Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: In more resent releases of bluez-util is there a new daemon that should be investigated if thats a more suitable way for newer releases
Created attachment 309063 [details] Changes to bluez-utils-3.7-2.el5
Created attachment 309064 [details] Default pincode
bluez-gnome (available in RHEL5) already contains a passkey agent for hcid to use, over D-Bus. Make sure bluetooth-applet is started on your system if you don't use GNOME as your desktop.
And since I don't have a Desktop, just a CLI how is this a fix for that ? Im sorry that I didn't state that the RFE was to solve a console/CLI situation since I don't have a Desktop on my servers, they just run the CLI.
For TUI installations, this is really needed. I would second this, hoping that a fix will be put in place. Tested myself with a custom compile and install and I'm not able to find any other way to get BlueTooth pairing working without the passkey-agent. Thanks LeeT
This feature should be addressed in upstream first. If you feel that this problem is critical for you, feel free to contact redhat.com/support to raise a priority of this issue.