FS#4930 - bluez-utils needs passkey-agent

Attached to Project: Arch Linux
Opened by Thomas Bächler (brain0) - Saturday, 01 July 2006, 13:44 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 11 February 2009, 19:57 GMT
Task Type Feature Request
Category Packages: Testing
Status Closed
Assigned To Geoffroy Carrier (gcarrier)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

bluez changed the pin_helper concept in the last release. If pairing with a device requires a PIN, then it will send a dbus-message. Unfortunately, there are currently no dbus helpers compatible with the new bluez dbus API.

There is a small program called passkey-agent in the bluez-utils source, which solves this problem. If you call "passkey-agent --default <pin>" just before the pairing attempt, it will use the right pin.

This program is built with bluez-utils, but make install ignores it.
Fix: Add install -D -m755 $startdir/src/bluez-utils-3.1/hcid/passkey-agent $startdir/pkg/usr/bin/passkey-agent to the PKGBUILD.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Wednesday, 11 February 2009, 19:57 GMT
Reason for closing:  Deferred
Additional comments about closing:  See  FS#12851  for bluez-4 series
Comment by Bartek Piech (delor) - Monday, 26 January 2009, 10:45 GMT
  • Field changed: Percent Complete (100% → 0%)
testing/bluez 4.25-2
same problem
Comment by Bartek Piech (delor) - Wednesday, 28 January 2009, 08:50 GMT
Related task #12851
Comment by Damjan Georgievski (damjan) - Wednesday, 28 January 2009, 16:36 GMT
This was probably solved in the bluez-3 series and #12851 seems open to be for bluez-4 series.. close bug?
Comment by Aaron Griffin (phrakture) - Wednesday, 28 January 2009, 17:31 GMT
Geoffroy, is this closable?

Loading...