Bluez PIN woes

[Doug Palmer]

I'm at my wits end here, so I'm hoping that someone has encountered this
problem before.

I'm trying to use Bluez to connect my Samsung Z350 phone to a box
running Fedora Core 6. I'm using the kdebluetooth system at the moment,
but the same thing is happening with obexftp, so the problem seems to be
connected with the Bluez stack itself.

When I try to connect to my phone, the phone pops up a dialog box asking
for a PIN, which I duly enter. I'm also expecting another dialog box to
pop up on the computer, also asking for a PIN so that the devices can
pair. Syslog shows that I am getting a request of the form

pin_code_request (sba=00:0A:3A:56:C5:16, dba=00:18:AF:3E:9C:16)

Reading around, it seems that I should be able to put a line with
pin_helper /usr/lib64/kdebluetooth/kbluepin; into
the /etc/bluetooth/hci.conf configuration file. But this program never
seems to be called. I've tried replacing it with a script that will log
its running to syslog, but that also never seems to be called.

All suggestions gratefully received.

Doug
--
linux mailing list
linux@...
https://lists.samba.org/mailman/listinfo/linux

Doug,

> Reading around, it seems that I should be able to put a line with
> pin_helper /usr/lib64/kdebluetooth/kbluepin; into
> the /etc/bluetooth/hci.conf configuration file. But this program
> never seems to be called. I've tried replacing it with a script that
> will log its running to syslog, but that also never seems to be
> called.

I'm using kubuntu and encoutered a similar problem. Hopefully this is
still relevant to fedora.

The new pin helper stuff uses dbus to get the PIN on connection, rather
than calling the pin helper directly. There's a passkey-agent program
that will wrap a standard pin-helper to add dbus support. To get it
running:

  passkey-agent --default /usr/lib/kdebluetooth/kbluepin

(this runs in my .xsession, so it just works on startup).

Hope this helps.


Jeremy
--
linux mailing list
linux@...
https://lists.samba.org/mailman/listinfo/linux

[Doug Palmer]

On Wed, 2007-02-21 at 11:06 +1100, Jeremy Kerr wrote:

Thanks for the quick reply.

>   passkey-agent --default /usr/lib/kdebluetooth/kbluepin

Ah. This would be the missing passkey-agent, then.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=212825

However, this has led me to finally get things going. What I need to do
is run the GNOME bluetooth-applet (that doesn't appear in the KDE
menus). This seem to be a substitute for passkey-agent that RedHat found
in a beautiful dream with monkeys in it. Once I do that, it all hangs
together nicely.

--
linux mailing list
linux@...
https://lists.samba.org/mailman/listinfo/linux