All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] key agent for bluez cli only
Date: Mon, 22 Sep 2008 22:48:13 +0200	[thread overview]
Message-ID: <48D8048D.7080904@powercraft.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

Hello everybody,

I am looking for a solution to sent a key when a device is requesting
this. I hope somebody can help me out, I have attached a log file, that
also include some found issues.

pin_code_request (sba=00:1B:DC:00:32:71, dba=00:0D:FD:18:6E:3C)
connect(): Permission denied (13)
discovery failed

ps. attachment include

Best regards,

Jelle



[-- Attachment #2: bluez.log --]
[-- Type: text/x-log, Size: 4022 bytes --]

Sep 22 22:38:57 debian-eeepc hidd[1908]: Exit
Sep 22 22:38:57 debian-eeepc hcid[1899]: Unregister path: /org/bluez/hci0
Sep 22 22:38:57 debian-eeepc hcid[1899]: Unregistered manager path
Sep 22 22:38:57 debian-eeepc hcid[1899]: Stopping SDP server
Sep 22 22:38:57 debian-eeepc hcid[1899]: Exit
Sep 22 22:38:58 debian-eeepc hcid[2432]: Bluetooth HCI daemon
Sep 22 22:38:58 debian-eeepc hcid[2432]: Parsing /etc/bluetooth/main.conf failed: No such file or directory
Sep 22 22:38:58 debian-eeepc hcid[2432]: Starting SDP server
Sep 22 22:38:58 debian-eeepc hcid[2432]: Unix socket created: 11
Sep 22 22:38:58 debian-eeepc hidd[2434]: Bluetooth HID daemon
Sep 22 22:38:58 debian-eeepc hcid[2432]: Registered manager path:/org/bluez/audio
Sep 22 22:38:58 debian-eeepc hcid[2432]: Loading device 00:0D:FD:18:6E:3C (headset sink control )
Sep 22 22:38:58 debian-eeepc hcid[2432]: Loading device 00:0C:55:D1:C9:78 (sink control )
Sep 22 22:38:58 debian-eeepc hcid[2432]: Setting 00:0C:55:D1:C9:78 as default device
Sep 22 22:38:58 debian-eeepc hcid[2432]: HCI dev 0 registered
Sep 22 22:38:58 debian-eeepc hcid[2432]: HCI dev 0 already up
Sep 22 22:38:58 debian-eeepc hcid[2432]: Device hci0 has been added
Sep 22 22:38:58 debian-eeepc hcid[2432]: Starting security manager 0
Sep 22 22:38:58 debian-eeepc hcid[2432]: Device hci0 has been activated
Sep 22 22:39:34 debian-eeepc hcid[2432]: Audio API: received BT_GETCAPABILITIES_REQ
Sep 22 22:39:38 debian-eeepc hcid[2432]: pin_code_request (sba=00:1B:DC:00:32:71, dba=00:0D:FD:18:6E:3C)
Sep 22 22:39:38 debian-eeepc hcid[2432]: connect(): Permission denied (13)
Sep 22 22:39:38 debian-eeepc hcid[2432]: discovery failed
Sep 22 22:39:38 debian-eeepc hcid[2432]: Audio API: sending BT_GETCAPABILITIES_RSP
Sep 22 22:39:39 debian-eeepc hcid[2432]: Audio API: received BT_GETCAPABILITIES_REQ
Sep 22 22:39:43 debian-eeepc hcid[2432]: pin_code_request (sba=00:1B:DC:00:32:71, dba=00:0D:FD:18:6E:3C)
Sep 22 22:39:43 debian-eeepc hcid[2432]: connect(): Permission denied (13)
Sep 22 22:39:43 debian-eeepc hcid[2432]: discovery failed
Sep 22 22:39:43 debian-eeepc hcid[2432]: Audio API: sending BT_GETCAPABILITIES_RSP
Sep 22 22:39:50 debian-eeepc hcid[2432]: Audio API: received BT_GETCAPABILITIES_REQ
Sep 22 22:39:53 debian-eeepc hcid[2432]: pin_code_request (sba=00:1B:DC:00:32:71, dba=00:0D:FD:18:6E:3C)
Sep 22 22:39:53 debian-eeepc hcid[2432]: connect(): Permission denied (13)
Sep 22 22:39:53 debian-eeepc hcid[2432]: discovery failed

sudo python /home/user/.simple-agent.py
ERROR:dbus.connection:Unable to set arguments ('/test/agent',) according to signature u'os': <type 'exceptions.TypeError'>: More items found in D-Bus signature than in Python arguments
Traceback (most recent call last):
  File "/home/jelle/.simple-agent.py", line 54, in <module>
    adapter.RegisterAgent(path)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 612, in call_blocking
    message.append(signature=signature, *args)
TypeError: More items found in D-Bus signature than in Python arguments

sudo /usr/share/doc/bluez-utils/examples/passkey-agent 0000 00:0D:FD:18:6E:3C
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.

Sep 22 22:42:07 debian-eeepc hcid[2432]: register_passkey_agent called without any adapter info!
Sep 22 22:42:38 debian-eeepc last message repeated 242381 times
Sep 22 22:43:39 debian-eeepc last message repeated 459396 times
Sep 22 22:44:40 debian-eeepc last message repeated 477043 times

ps aux | grep hcid (high cpu load need to sudo killall -9 hcid)
root      2432 18.8  0.3   3452  1640 ?        Rs   22:38   0:57 /usr/sbin/hcid -x -s

[-- Attachment #3: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-09-22 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 20:48 Jelle de Jong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-22 20:47 [Bluez-devel] key agent for bluez cli only Jelle de Jong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48D8048D.7080904@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.