[Pkg-bluetooth-maintainers] Bug#384188: bluez-utils: pairing fails
from PC to mobile, but succeeds the other way
Mathias Behrle
mathias.behrle at gmx.de
Wed Sep 6 16:24:29 UTC 2006
Package: bluez-utils
Version: 3.1-4
Followup-For: Bug #384188
I don't know, if this belongs really to this bug, but instead of opening a new one I prefer to provide additional information:
I followed all described procedures to put passkeys in /etc/bluetooth/default and resp. /etc/bluetooth/00:0E:07:8A:1E:FD sticking for the rest to the Debain default configuration.
Sep 6 17:09:57 localhost hcid[10453]: Bluetooth HCI daemon
Sep 6 17:09:57 localhost hcid[10453]: Register path:/org/bluez fallback:1
Sep 6 17:09:57 localhost hcid[10453]: Device hci0 has been added
Sep 6 17:09:57 localhost hcid[10453]: Starting security manager 0
Sep 6 17:09:57 localhost sdpd[10457]: Bluetooth SDP daemon
Sep 6 17:09:57 localhost hcid[10453]: Can't write inquiry mode for hci0: Input/output error (5)
Sep 6 17:09:57 localhost hcid[10453]: Register path:/org/bluez/hci0 fallback:0
Sep 6 17:09:57 localhost hcid[10453]: name_listener_add(:1.12)
Sep 6 17:09:57 localhost hcid[10453]: name_listener_add(:1.13)
Sep 6 17:09:57 localhost hcid[10453]: Default passkey agent (:1.13, /org/bluez/passkey_agent_10472) registered
I could connect via
hcitool cc 00:0E:07:8A:1E:FD
but
hcitool auth 00:0E:07:8A:1E:FD said:
HCI authentication request failed: Input/output error
Trying to connect with kbluetooth I got the Popup on the mobile to enter the PIN, but every time I was said, that the PIN was wrong (giving the correct PIN of course;-).
Also I couldn't discover the dongle at the PC with my mobile, which was solved according to another bug report with
dbus-send --system --dest=org.bluez /org/bluez/hci0 \
org.bluez.Adapter.SetMode string:discoverable
Discovering and Pairing from the mobile then succeeded as usual.
I had no problems so far, always upgrading to the testing version of bluez-utils. The problem appeared, because I used the dongle on another machine pairing with just this mobile
(so the dongle got another name in the mobile). To enable a clean new discovery I deleted the device on the mobile. Now device could not be (re)established.
After discovering and pairing the dongle from the mobile all applications are running again.
Mathias
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (800, 'unstable'), (600, 'experimental'), (400, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-md-dm-static-suspend2-asterix
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages bluez-utils depends on:
ii dbus 0.62-4 simple interprocess messaging syst
ii libbluetooth2 3.1-1 Library to use the BlueZ Linux Blu
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libdbus-1-2 0.62-4 simple interprocess messaging syst
ii libdbus-glib-1-2 0.62-4 simple interprocess messaging syst
ii libglib2.0-0 2.10.3-3 The GLib library of C routines
ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library
ii lsb-base 3.1-15 Linux Standard Base 3.1 init scrip
ii makedev 2.3.1-82 creates device files in /dev
ii module-init-tools 3.2.2-3 tools for managing Linux kernel mo
ii modutils 2.4.27.0-6 Linux module utilities
ii sysvinit 2.86.ds1-15 System-V-like init utilities
bluez-utils recommends no packages.
-- debconf-show failed
More information about the Pkg-bluetooth-maintainers
mailing list