Filippo Giunchedi wrote: > On Thu, Jun 25, 2009 at 07:58:01AM +0200, Harald Dunkel wrote: >>> =20 >>> I'd like if you can try this: >>> =20 >>> dbus-send --system --print-reply --dest=3Dorg.bluez / \ >>> org.bluez.Manager.DefaultAdapter >>> =20 >>> this will give you an object path with the default adapter. >>> Start bluetooth-agent providing a passkey, then: >>> =20 >> bluetooth-agent 0000 >> >> got stuck :-(. This is the new bluez 4.42, of course. > > what do you mean "got stuck" ? >
I mean I ran "bluetooth-agent 0000", but it just sits there. It doesn't print any message, nor does it return, regardless whether the headphone is in pairing mode. Attached you can find the strace. AFAICS it expects a message from a dbus socket. Dbus is running: % ps -ef | grep [d]bus 104 3066 1 0 17:29 ? 00:00:00 /usr/bin/dbus-daemon --system harri 3988 3886 0 17:29 tty1 00:00:00 xinit /usr/bin/dbus-launch --exit-with-session /export/harri/.xinitrc -- :4 -br -quiet harri 4046 1 0 17:29 tty1 00:00:00 /usr/bin/dbus-launch --exit-with-session /export/harri/.xinitrc harri 4047 1 0 17:29 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session The socket is readable, too: % ls -al /var/run/dbus/system_bus_socket srwxrwxrwx 1 root root 0 Jun 25 17:29 /var/run/dbus/system_bus_socket
bt.log.gz
Description: Unix tar archive
signature.asc
Description: OpenPGP digital signature
