All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users]  dbus agent problem
Date: Sat, 24 May 2008 17:26:32 +0200	[thread overview]
Message-ID: <483833A8.3000404@powercraft.nl> (raw)

Hello everybody

I am still trying to get my bluetooth headset working again, the problem
is that my dbus agent does not work anymore!

I would like to have a checklist what is needed to have an functional agent.

As you can see there is no key send to the device anymore and the agent
is not working, so i would really appreciate a checklist what is needed
to have a functional agent.

Thanks in advance,

Kind regards,

Jelle

-- -- -- --

May 24 17:24:14 debian-eeepc hcid[2511]: Bluetooth HCI daemon
May 24 17:24:14 debian-eeepc hcid[2511]: HCI dev 0 registered
May 24 17:24:14 debian-eeepc hcid[2511]: HCI dev 0 already up
May 24 17:24:14 debian-eeepc hcid[2511]: Device hci0 has been added
May 24 17:24:14 debian-eeepc hcid[2511]: Starting security manager 0
May 24 17:24:14 debian-eeepc hcid[2511]: Device hci0 has been activated
May 24 17:24:14 debian-eeepc hcid[2511]: Starting SDP server
May 24 17:24:14 debian-eeepc hcid[2511]: Unix socket created: 13
May 24 17:24:14 debian-eeepc hcid[2511]: Registered manager 
path:/org/bluez/audio
May 24 17:24:14 debian-eeepc hcid[2511]: Registering service
May 24 17:24:47 debian-eeepc hcid[2511]: Audio API: received 
BT_GETCAPABILITIES_REQ
May 24 17:24:48 debian-eeepc hcid[2511]: pin_code_request 
(sba=00:1B:DC:00:32:71, dba=00:0D:FD:18:6E:3C)
May 24 17:25:12 debian-eeepc hcid[2511]: GetRemoteServiceHandles failed: 
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.
May 24 17:25:12 debian-eeepc hcid[2511]: Audio API: sending 
BT_GETCAPABILITIES_RSP
May 24 17:25:12 debian-eeepc hcid[2511]: Unregistered device 
path:/org/bluez/audio/device0
May 24 17:25:13 debian-eeepc hcid[2511]: Audio API: received 
BT_GETCAPABILITIES_REQ
May 24 17:25:13 debian-eeepc hcid[2511]: GetRemoteServiceHandles failed: 
Service search in progress
May 24 17:25:13 debian-eeepc hcid[2511]: Audio API: sending 
BT_GETCAPABILITIES_RSP
May 24 17:25:13 debian-eeepc hcid[2511]: Unregistered device 
path:/org/bluez/audio/device1
May 24 17:25:14 debian-eeepc hcid[2511]: Audio API: received 
BT_GETCAPABILITIES_REQ
May 24 17:25:14 debian-eeepc hcid[2511]: GetRemoteServiceHandles failed: 
Service search in progress
May 24 17:25:14 debian-eeepc hcid[2511]: Audio API: sending 
BT_GETCAPABILITIES_RSP
May 24 17:25:14 debian-eeepc hcid[2511]: Unregistered device 
path:/org/bluez/audio/device2
May 24 17:25:15 debian-eeepc hcid[2511]: Audio API: received 
BT_GETCAPABILITIES_REQ
May 24 17:25:15 debian-eeepc hcid[2511]: GetRemoteServiceHandles failed: 
Service search in progress
May 24 17:25:15 debian-eeepc hcid[2511]: Audio API: sending 
BT_GETCAPABILITIES_RSP
May 24 17:25:15 debian-eeepc hcid[2511]: Unregistered device 
path:/org/bluez/audio/device3
May 24 17:25:16 debian-eeepc hcid[2511]: Audio API: received 
BT_GETCAPABILITIES_REQ
May 24 17:25:16 debian-eeepc hcid[2511]: GetRemoteServiceHandles failed: 
Service search in progress
May 24 17:25:16 debian-eeepc hcid[2511]: Audio API: sending 
BT_GETCAPABILITIES_RSP
May 24 17:25:16 debian-eeepc hcid[2511]: Unregistered device 
path:/org/bluez/audio/device4
May 24 17:25:17 debian-eeepc hcid[2511]: Audio API: received 
BT_GETCAPABILITIES_REQ
May 24 17:25:17 debian-eeepc hcid[2511]: GetRemoteServiceHandles failed: 
Service search in progress
May 24 17:25:17 debian-eeepc hcid[2511]: Audio API: sending 
BT_GETCAPABILITIES_RSP
May 24 17:25:17 debian-eeepc hcid[2511]: Unregistered device 
path:/org/bluez/audio/device5
May 24 17:25:17 debian-eeepc hcid[2511]: connect(): Function not 
implemented (38)
May 24 17:25:18 debian-eeepc hcid[2511]: Audio API: received 
BT_GETCAPABILITIES_REQ
May 24 17:25:18 debian-eeepc hcid[2511]: pin_code_request 
(sba=00:1B:DC:00:32:71, dba=00:0D:FD:18:6E:3C)
May 24 17:25:18 debian-eeepc kernel: hcid[2511]: segfault at 00000010 
eip 080619e5 esp bfcecff0 error 6

-- -- -- --

sudo /etc/init.d/bluetooth stop
sudo /etc/init.d/alsa-utils stop
echo | sudo tee /var/log/syslog
sudo rm --recursive /var/lib/bluetooth/*

echo 'pcm.headset {
      type bluetooth
      #~ device 00:0D:18:A0:35:70
      #~ device 00:53:53:FB:7E:9C # Nokia BH-801
      #~ device 00:0C:55:D1:C9:78 # Motorola S805
      device 00:0D:FD:18:6E:3C # Motorolas S9
      #~ device 20:07:09:15:A9:5A # Samsung WEP210
      profile hifi
      #~ profile voice
      #profile auto
}
pcm.softvol {
      type softvol
      slave.pcm headset
      control.name Headset
      control.card 0
}
pcm.!default {
      #~ type hw
      #~ card 0
      type plug
      slave.pcm softvol
}' | tee $HOME/.asoundrc

echo 'options {
      autoinit yes;
      security auto;
      pairing multi;
      passkey "0000";
}
device {
      name "BlueZ (%d)";
      class 0x000100;
      iscan enable; pscan enable;
      lm accept,master;
      lp hold,sniff,park;
}' | sudo tee /etc/bluetooth/hcid.conf

sudo /etc/init.d/sysklogd restart
sudo /etc/init.d/klogd restart
sudo /etc/init.d/bluetooth restart
sudo /etc/init.d/alsa-utils restart
sudo python $HOME/.simple-agent.py
echo done

sudo tail --lines=100 --follow /var/log/syslog

speaker-test -c2

-- -- -- --
http://filebin.ca/kojejg/simple-agent

#!/usr/bin/python

import gobject

import dbus
import dbus.service
import dbus.mainloop.glib

class Agent(dbus.service.Object):
      @dbus.service.method("org.bluez.Agent",
                      in_signature="", out_signature="")
      def Release(self):
          print "Release"
          mainloop.quit()

      @dbus.service.method("org.bluez.Agent",
                      in_signature="os", out_signature="")
      def Authorize(self, device, uuid):
          print "Authorize (" + device + ", " + uuid + ")"
          return

      @dbus.service.method("org.bluez.Agent",
                      in_signature="o", out_signature="s")
      def RequestPasskey(self, device):
          print "RequestPasskey (" + device + ")"
          return "0000"

      @dbus.service.method("org.bluez.Agent",
                      in_signature="s", out_signature="")
      def ConfirmModeChange(self, mode):
          print "ConfirmModeChange (" + mode + ")"
          return

      @dbus.service.method("org.bluez.Agent",
                      in_signature="", out_signature="")
      def Cancel(self):
          print "Cancel"
          return

if __name__ == '__main__':
      dbus.mainloop.glib.DBusGMainLoop(set_as_default=True)

      bus = dbus.SystemBus()
      manager = dbus.Interface(bus.get_object("org.bluez", "/"),
                              "org.bluez.Manager")

      path = manager.DefaultAdapter()
      adapter = dbus.Interface(bus.get_object("org.bluez", path),
                              "org.bluez.Adapter")

      path = "/test/agent"
      object = Agent(bus, path)

      adapter.RegisterAgent(path)
      print "Agent registered"

      mainloop = gobject.MainLoop()
      mainloop.run()

      #adapter.UnregisterAgent(path)
      #print "Agent unregistered"

-- -- -- --

cat /etc/dbus-1/system.d/bluetooth.conf
<!-- This configuration file specifies the required security policies
       for Bluetooth core service to work. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration
1.0//EN"
   "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

    <!-- ../system.conf have denied everything, so we just punch some
holes -->

    <policy user="root">
      <allow own="org.bluez"/>
    </policy>

    <policy at_console="true">
      <allow send_destination="org.bluez.Manager"/>
      <allow receive_sender="org.bluez.Manager"/>

      <allow send_path="/org/bluez"/>

      <allow send_destination="org.bluez.Adapter"/>
      <allow receive_sender="org.bluez.Adapter"/>

      <allow send_destination="org.bluez.Service"/>
      <allow receive_sender="org.bluez.Service"/>

      <allow send_destination="org.bluez.Database"/>
      <allow receive_sender="org.bluez.Database"/>

      <allow send_destination="org.bluez.Security"/>
      <allow receive_sender="org.bluez.Security"/>
    </policy>

</busconfig>

-- -- -- -- --

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2008-05-24 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-24 15:26 Jelle de Jong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-24 14:53 [Bluez-users] dbus agent problem 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=483833A8.3000404@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=bluez-users@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.