Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
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
|
Detailsbluez 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
Wednesday, 11 February 2009, 19:57 GMT
Reason for closing: Deferred
Additional comments about closing: See
same problem