[Bug 21926] Re: Bluetooth pairing outgoing connections does not work unless you restart bluez services

[gcc]

For the record, I have the exact same problem on Feisty (7.04). Is it
WONTFIX for Feisty?

chris at rocio:~$ hcitool cc --role=m 00:1C:CC:4C:15:98
Can't create connection: Operation not permitted

chris at rocio:~$ sudo hcitool cc --role=m 00:1C:CC:4C:15:98
(phone prompts for PIN; when I enter it, I get this:)
Can't create connection: Input/output error

chris at rocio:~$ sudo tail -2 /var/log/daemon.log
Dec 24 11:37:55 rocio hcid[6925]: pin_code_request (sba=00:20:E0:78:20:9F, dba=00:1C:CC:4C:15:98)
Dec 24 11:39:28 rocio hcid[6925]: pin_code_request (sba=00:20:E0:78:20:9F, dba=00:1C:CC:4C:15:98)

chris at rocio:~$ sudo /etc/init.d/bluetooth restart
 * Restarting Bluetooth services                                         [ OK ] 
chris at rocio:~$ sudo hcitool cc --role=m 00:1C:CC:4C:15:98
Can't create connection: Input/output error
(same as before, restarting doesn't help)

chris at rocio:~/project/boxi/cppunit-1.10.2$ hcid -n
hcid[6581]: Bluetooth HCI daemon
hcid[6581]: Could not become the primary owner of org.bluez
hcid[6581]: Unable to get on D-Bus

chris at rocio:~/project/boxi/cppunit-1.10.2$ sudo hcid -n
hcid[6593]: Bluetooth HCI daemon
hcid[6593]: Could not become the primary owner of org.bluez
hcid[6593]: Unable to get on D-Bus

If I kill the existing hcid and run it again, then hcitool again:

chris at rocio:~$ ps auxww  |grep hcid
root      7378  0.0  0.1   2700  1076 ?        Ss   12:40   0:00 /usr/sbin/hcid -x -s
chris at rocio:~$ sudo kill 7378
chris at rocio:~$ sudo hcid -n -x -s
hcid[7500]: Bluetooth HCI daemon
hcid[7500]: HCI dev 0 registered
hcid[7500]: HCI dev 0 already up
hcid[7500]: Device hci0 has been added
hcid[7500]: Starting security manager 0
hcid[7500]: Device hci0 has been activated
hcid[7500]: Starting SDP server
hcid[7500]: pin_code_request (sba=00:20:E0:78:20:9F, dba=00:1C:CC:4C:15:98)

No indication why pairing failed.

I tried to follow the instructions on
https://launchpad.net/ubuntu/+source/bluez-utils/+bug/59222 , but:

* kbluezpin doesn't work due to an incompatible DBUS interface:

chris at rocio:~$ passkey-agent --default /usr/lib/kdebluetooth/kbluepin
Passkey request for device 00:1C:CC:4C:15:98
Invalid arguments for passkey Request method

* bluez-passkey-gnome package doesn't exist
* bluez-gnome doesn't appear to contain a passkey application

So there appears to be no valid passkey helper in feisty.

Also there seems to be a bug in bluez-libs (even latest version) where
it reports an error after asking the device for a PIN and receiving a
response (Can't create connection: Input/output error, as above). I
traced it into hci_create_connection and then got lost in Bluetooth
protocol. From strace, it tries to seek on stderr, which isn't allowed:

chris at rocio:~$ sudo strace -f hcitool cc --role=m 00:1C:CC:4C:15:98
read(3, "\4\17\4\0\1\5\4", 260)         = 7
poll([{fd=3, events=POLLIN, revents=POLLIN}], 1, 24990) = 1
read(3, "\4\3\v\30)\0\230\25L\314\34\0\1\0", 260) = 14
setsockopt(3, SOL_IP, IP_TTL, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 16) = 0
dup(2)                                  = 4
fcntl64(4, F_GETFL)                     = 0x2 (flags O_RDWR)
fstat64(4, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 8), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f5a000
_llseek(4, 0, 0xbf9b4f24, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
write(4, "Can\'t create connection: Input/o"..., 44Can't create connection: Input/output error

(note that fd 4 is dup(2) which is stderr).

-- 
Bluetooth pairing outgoing connections does not work unless you restart bluez services
https://bugs.launchpad.net/bugs/21926
You received this bug notification because you are a member of
Bluetooth, which is a bug contact for bluez-utils in ubuntu.