« Return to Thread: Bluez PIN woes

Re: Bluez PIN woes

by Bugzilla from jk@ozlabs.org :: Rate this Message:

Reply to Author | View in Thread

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

 « Return to Thread: Bluez PIN woes