Bug#385857: [Pkg-bluetooth-maintainers] Bug#385857: please upgrade to bluez-utils and bluez-libs 3.4

[Marcel Holtmann]

Hi Flavio,

> Package: bluez-utils
> Version: 3.1-4
> Severity: wishlist
> 
> Yesterday I bought a Bluetooth USB dongle to connect with my mobile
> phone, but I had some problems with discovery and sending files from
> phone to computer. I'm using bluez-utils and kdebluetooth on Debian
> testing/unstable.
> 
> The problem with discovery was the well-known issue with ISCAN, but
> after I fixed that I still wasn't able to send files from phone to
> computer. Finally I packaged bluez-libs and bluez-utils 3.4 and it
> worked at the first try, so I suspect the "couple of issues of the D-Bus
> based API" fixed in 3.2, 3.3 and 3.4 are significant after all.

the 3.5 is coming really soon and fixes another couple of rare race
conditions that can lead to segmentation faults of hcid. The 3.1 version
is not really suited for daily use.

> bluez-libs compiled out of the box by just unpacking and moving the
> debian directory over, but bluez-utils needs some work:
> 
> * remove bluez-bcm203x package (bcm203x firmware loader removed upstream)

Not needed at all. You don't wanna support a 2.4 kernel and even if you
really want to, you won't find any of these devices anymore. For all 2.6
kernels the bcm203x kernel module takes care of loading the firmware.

This package has to die and from an USB and udev perspective it was a
really nasty hack.

> * remove 000_rfcomm_conf_example.patch: the example is already commented
> * remove 004_rfcomm_usage.patch: applied upstream

Sometimes it is a good idea to feed patches back to upstream so I don't
have to extract them from the packages.

> Also note that apparently it is important to remove leftover stuff from
> /var/lib/bluetooth/<device> to fix the ISCAN issue; it is also probably
> a good idea to add "discovto 0;" to the default configuration file (see
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384379).

Adding discovto makes a device more insecure. It should go back to
non-discoverable mode unless the user configures it otherwise.

And removing all files from /var/lib/bluetooth is a really bad idea. You
will also remove link keys and the name cache. If you wanna reset the
settings then only look at the config files (plural, because some people
actually use multiple adapters) in that directory. However I wouldn't
advise to touch the configuration storage at all.

> Finally, upstream added udev rules for Bluetooth serial PCMCIA cards; I
> don't know if these udev rules are useful.

They are a fully replacement for the ones in the Debian package. That is
another thing that always needs to be discussed with upstream.

To install them --enable-pcmciarules is needed and the correct configure
call. Example is in the README. Otherwise the wrong directory will be
picked for them.

> -- System Information:
> Debian Release: testing/unstable
>   APT prefers testing
>   APT policy: (500, 'testing'), (10, 'unstable')
> Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.17.11-athlon
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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-15    GNU C Library: Shared libraries
> ii  libdbus-1-2                  0.62-4      simple interprocess messaging syst
> ii  libusb-0.1-4                 2:0.1.12-2  userspace USB programming library
> ii  lsb-base                     3.1-14      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
> ii  udev                         0.093-1     /dev/ and hotplug management daemo
> 
> bluez-utils recommends no packages.
> 
> -- no debconf information