LinuxQuestions.org - Bluetooth Pairing Fails

Hello,

First some system details:

]# cat /etc/redhat-release
Red Hat Enterprise Linux Client release 5.6 (Tikanga)

]# uname -a
Linux mycomputer 2.6.18-238.el5PAE #1 SMP Sun Dec 19 14:42:44 EST 2010 i686 i686 i386 GNU/Linux

]# rpm -qa | grep blue
bluez-gnome-0.5-5.fc6
gnome-bluetooth-libs-0.7.0-10.2.el5
bluez-hcidump-1.32-1
bluez-libs-3.36-1
bluez-utils-3.36-1

Problem Description:
I see two problems and would like to resolve both but initially focus on the shortes path to pairing my device, if possible.

1. GUI doesn't work the way I have seen it represented. I see the Bluetooth Manager icon in the system tray. When I mouse-over it a pop-up showing "Bluetooth Manager" appears. When I right-click on the icon I only get two menu options: Discoverable (with a checkbox) and About. The other options appear to be missing.

2. Pairing fails. I have a Bluetooth USB device installed and recognized but pairing simply doesn't work.

Bluetooth Device: IOGear Bluetooth 2.1 USB Micro Adapter

]# /etc/init.d/bluetooth restart
Stopping Bluetooth services: [ OK ]
Starting Bluetooth services: [ OK ]

]# hciconfig -a
hci0: Type: USB
BD Address: 00:02:72:AF:F0:B0 ACL MTU: 1021:7 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:1226 acl:0 sco:0 events:60 errors:0
TX bytes:1280 acl:0 sco:0 commands:47 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'mycomputer-0'
Class: 0x080100
Service Classes: Capturing
Device Class: Computer, Uncategorized
HCI Ver: 2.1 (0x4) HCI Rev: 0x5332 LMP Ver: 2.1 (0x4) LMP Subver: 0x420e
Manufacturer: Broadcom Corporation (15)

]# hcitool scan
Scanning ...
00:23:7F:2A:25:DF Calisto PLT

]# passkey-agent 0000 00:23:7F:2A:25:DF &
[1] 28665

]# hcitool cc 00:23:7F:2A:25:DF
Can't register passkey agent
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

I hope I have provided enough information to troubleshoot. Please let me know if I have left anything out.

Thanks!