Package: bluez-utils Version: 3.7-1 Followup-For: Bug #382269
I ran into the same problem: cannot (re)establish a pairing because there is no working pin agent, and trying to install bluez-pin wants to remove bluez-utils. I tried bluetooth-applet, but it did not come up with a pin request at the right time (according to the syslog it did register as bluetooth pin agent). I use fvwm as window manager. I tried multiple ways of entering the pin in the filesystem, none of which worked. Looking at /etc/bluetooth/passkeys/* shows none of those were read by the bluez-utils processes. In the end, I found https://launchpad.net/ubuntu/+source/bluez-utils/+bug/56651 where 'Dan V' shows a workaround to getting at least the passkey-agent compiled. I got far enough to have a compiled passkey-agent, and that worked for the one pairing I needed. Yes, this is quite frustrating, when the basic utilities (bluez-utils) cannot be installed at the same time as a basic pincode agent (bluez-pin). I hope the above url helps people who need a quick fix. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.32 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages bluez-utils depends on: ii dbus 1.0.2-1 simple interprocess messaging syst ii libbluetooth2 3.7-1 Library to use the BlueZ Linux Blu ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii lsb-base 3.1-23 Linux Standard Base 3.1 init scrip ii makedev 2.3.1-83 creates device files in /dev ii module-init-tools 3.3-pre4-1 tools for managing Linux kernel mo ii modutils 2.4.27.0-6 Linux module utilities Versions of packages bluez-utils recommends: ii bluez-gnome [bluez-passkey-gn 0.6-1 Bluetooth utilities for GNOME -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]