[Pkg-bluetooth-maintainers] Bug#384379: bluez-utils: problem still not fixed

[Armin Berres]

Package: bluez-utils
Version: 3.7-1
Followup-For: Bug #384379

This bug is still not fixed in 3.7-1.
I tried adding "discovto 0;" to hcid.conf, sending a message with dbus, module
unloading/loading, but nothing changed the situation.
I still get something like this:
---------------------------------------
# hciconfig -a
hci0:   Type: USB
        BD Address: 00:00:3A:69:0E:9C ACL MTU: 1017:8 SCO MTU: 64:8
        UP RUNNING PSCAN
---------------------------------------
IMO this bug should really be fixed in time for Etch if possible.

/Armin

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages bluez-utils depends on:
ii  dbus                         1.0.1-2     simple interprocess messaging syst
ii  libbluetooth2                3.7-1       Library to use the BlueZ Linux Blu
ii  libc6                        2.3.6.ds1-8 GNU C Library: Shared libraries
ii  libdbus-1-3                  1.0.1-2     simple interprocess messaging syst
ii  libusb-0.1-4                 2:0.1.12-2  userspace USB programming library
ii  lsb-base                     3.1-22      Linux Standard Base 3.1 init scrip
ii  makedev                      2.3.1-83    creates device files in /dev
ii  module-init-tools            3.3-pre3-1  tools for managing Linux kernel mo
ii  modutils                     2.4.27.0-6  Linux module utilities
ii  udev                         0.103-1     /dev/ and hotplug management daemo

Versions of packages bluez-utils recommends:
ii  bluez-gnome [bluez-passkey-gn 0.6-1      Bluetooth utilities for GNOME
ii  bluez-passkey-gnome           0.5-2      Bluetooth passkey (PIN) agent for 

-- no debconf information